Skip to main content
Glama

apis_io_search

Read-only

START HERE. Federated overview of the APIs.io catalog for a query: the top matching APIs, providers, AND tags in one call, each with its total match count. Filter by tags, artifact types, industry, region, rating band. limit is per section. To page/sort the full list of ONE type, use find_apis / find_providers / find_tags; for one entity, get_api / get_provider.

Input Schema

NameRequiredDescriptionDefault
qNoFree text over name + description, e.g. "sms".
areaNoArea slugs, e.g. ["security"].
bandNoexemplar | strong | developing | thin | minimal.
sortNoDefault: relevance with `q`, else composite.
tagsNoTag slugs, e.g. ["payments"]. On providers: what the company does (see api_tags).
limitNoTop matches to return per section (apis/providers/tags).
matchNoHow `tags` combine: any (default) or all.any
regionNoRegion slugs, e.g. ["north-america"].
returnNoReturn only this kind of match. Default: every kind.
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
industryNoIndustry slugs, e.g. ["fintech"].
min_scoreNoMinimum Kin Score composite (0-100), e.g. 60.
providersNoProvider slugs to restrict all three sections to, e.g. ["stripe"].
artifact_typesNoArtifact types required, e.g. ["OpenAPI"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Area slugs, as find_areas returns them, e.g. [\"security\"]."New value: +"Area slugs, e.g. [\"security\"]."
    • changedInput schema / properties / artifact_types / description
      Previous value: -"Artifact types an API must carry, e.g. [\"OpenAPI\",\"AsyncAPI\",\"Postman\"]. Synonyms fold (MCPServer = MCP)."New value: +"Artifact types required, e.g. [\"OpenAPI\"]."
    • changedInput schema / properties / band / description
      Previous value: -"Rating bands: exemplar, strong, developing, thin, minimal."New value: +"exemplar | strong | developing | thin | minimal."
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / industry / description
      Previous value: -"Industry slugs, as find_industries returns them, e.g. [\"artificial-intelligence\"]."New value: +"Industry slugs, e.g. [\"fintech\"]."
    • changedInput schema / properties / match / description
      Previous value: -"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."New value: +"How `tags` combine: any (default) or all."
    • changedInput schema / properties / min_score / description
      Previous value: -"Only providers whose Kin Score composite is at or above this, 0-100, e.g. 60."New value: +"Minimum Kin Score composite (0-100), e.g. 60."
    • changedInput schema / properties / q / description
      Previous value: -"Free text over name + description."New value: +"Free text over name + description, e.g. \"sms\"."
    • changedInput schema / properties / region / description
      Previous value: -"Region slugs, as find_regions returns them, e.g. [\"north-america\"]."New value: +"Region slugs, e.g. [\"north-america\"]."
    • changedInput schema / properties / sort / description
      Previous value: -"Order results. Default: relevance with a query, composite (quality) when browsing. `demand` = Fortune-1000 adoption, scoped to the query."New value: +"Default: relevance with `q`, else composite."
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it."New value: +"Tag slugs, e.g. [\"payments\"]. On providers: what the company does (see api_tags)."
  2. Changed7 schema fields changed
    • addedInput schema / properties / area / description
      Added value: +"Area slugs, as find_areas returns them, e.g. [\"security\"]."
    • addedInput schema / properties / artifact_types / description
      Added value: +"Artifact types an API must carry, e.g. [\"OpenAPI\",\"AsyncAPI\",\"Postman\"]. Synonyms fold (MCPServer = MCP)."
    • addedInput schema / properties / industry / description
      Added value: +"Industry slugs, as find_industries returns them, e.g. [\"artificial-intelligence\"]."
    • addedInput schema / properties / match / description
      Added value: +"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."
    • addedInput schema / properties / min_score / description
      Added value: +"Only providers whose Kin Score composite is at or above this, 0-100, e.g. 60."
    • addedInput schema / properties / providers / description
      Added value: +"Provider slugs to restrict all three sections to, e.g. [\"stripe\"]."
    • addedInput schema / properties / region / description
      Added value: +"Region slugs, as find_regions returns them, e.g. [\"north-america\"]."
  3. Changed1 schema field changed
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or find_providers?api_tags= to reach companies whose APIs merely touch it."
  4. Changed1 schema field changed
    • addedInput schema / properties / return
      Added value: +{
      +  "description": "Return only this kind of match. Default: every kind.",
      +  "enum": [
      +    "apis",
      +    "providers",
      +    "tags"
      +  ],
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / tags / description
      Previous value: -"Tag slugs."New value: +"Tag slugs. On PROVIDERS this is identity — what the company says it does, from its own apis.yml. A resource or operation term (webhook, saml, order, oai-pmh) will correctly match no provider; use find_apis?tags= for those, or api_tags below."
  6. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
      +  "type": "string"
      +}
  7. Changed8 schema fields changed
    • removedInput schema / properties / fields
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • changedInput schema / properties / limit / default
      Previous value: -25New value: +5
    • addedInput schema / properties / limit / description
      Added value: +"Top matches to return per section (apis/providers/tags)."
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +25
    • removedInput schema / properties / page
      Removed value: -{
      -  "default": 1,
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • removedInput schema / properties / return
      Removed value: -{
      -  "default": "apis",
      -  "enum": [
      -    "apis",
      -    "providers",
      -    "tags"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / sort / description
      Added value: +"Order results. Default: relevance with a query, composite (quality) when browsing. `demand` = Fortune-1000 adoption, scoped to the query."
    • addedInput schema / properties / sort / enum
      Added value: +[
      +  "relevance",
      +  "composite",
      +  "name",
      +  "created",
      +  "modified",
      +  "api_count",
      +  "demand"
      +]
  8. Changed1 schema field changed
    • addedInput schema / properties / area
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  9. First observed

TDQS

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe read against a closed catalog. The description adds that results are top matches per section with total match counts, which is useful return-shape context. It does not elaborate on pagination limits, authentication, or ranking behavior beyond what the annotations and schema provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with 'START HERE' and then proceeds in compact, information-dense sentences. Every sentence earns its place by covering purpose, filters, limit behavior, and alternatives. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 14 optional parameters and no output schema, the description explains the federated return shape, what each section contains, and how results are scoped. It also routes the agent to alternatives when pagination or single-type listing is needed. Nothing critical for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all 14 parameters, including enums and defaults. The description reinforces the filter categories and clarifies that limit applies per section, but it adds little syntax or semantics beyond the schema. A baseline score of 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: a federated search of the APIs.io catalog across APIs, providers, and tags. It clearly differentiates this federated overview from the sibling type-specific search and entity-lookup tools. An agent can tell exactly what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance with 'START HERE' and directly names alternatives for other needs: use find_apis / find_providers / find_tags for paging or sorting a full list of one type, and get_api / get_provider for a single entity. It also states the supported filter dimensions. This is strong when-to-use and when-to-use-something-else guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources