/glama/attributes

POST /api/glama/attributes

Price: 1 credit

List every attribute tag Glama classifies MCP servers and connectors with. Returns each tag's lookup key, display name, the group it belongs to, its description, and how many servers and hosted connectors carry it. The groups cover subject category, implementation language, MCP capability, hosting model, runtime environment and authentication.

How to use it

Call this before filtering: `lookup_key` is the exact string the `attributes` parameter of /glama/servers/search and /glama/connectors/search takes, and a key that is not in this list is not applied. `server_count` and `connector_count` tell you how large a slice a tag will produce, which matters because either search stops at 1000 rows — a tag with a bigger count has to be combined with another to be enumerable.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of attributes to return (examples: 200; min: 1; max: 500)
• group string nullable — Keep only attributes belonging to this group, as the group is named in the catalog (examples: "Categories", "Languages", "Hosting"; minLength: 1)

Response

• @type string (default: "GlamaAttribute")
• lookup_key string required
• name string nullable
• group string nullable
• description string nullable
• icon string nullable
• server_count integer nullable
• connector_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.