Skip to main content
Glama

find_apis

Read-only

Paginated, sortable list of APIs across providers — filter by tag, provider, artifact type, industry, region, or rating band. Matching is LEXICAL: q searches the API's own name and description. apis_io_search reports a larger API total for the same q because it also counts every API belonging to a provider whose NAME matched; pass include=["via_provider"] here to get that same union, and meta.query.via_provider says how many rows it added. Use apis_io_search first for a cross-type overview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree text over name + description.
areaNo
bandNoRating bands: exemplar, strong, developing, thin, minimal.
pageNo
sortNoOrder results. Default: relevance with a query, composite (quality) when browsing. `demand` = Fortune-1000 adoption, scoped to the query.
tagsNoTag 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.
viewNosummary (default) returns lean discovery records + *_count for dropped sections; full returns the whole record (use get_api / get_provider for one entity).summary
limitNo
matchNoany
fieldsNoReturn exactly these top-level keys (overrides view).
publicNoOnly providers callable publicly with no signup (onboarding=open). (providers only)
regionNo
contextNoOptional: 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.
includeNovia_provider — also return the APIs of providers whose name matched `q`, the union apis_io_search counts. Needs `q`; adds nothing without one.
pricingNoAccess model — pricing: free, freemium, free-trial, paid, enterprise. (providers only)
resolveNoWhen `q` exactly names a tag, apis.io uses it: on PROVIDERS a resource tag (order, webhook, image) replaces the text search with the companies that classify themselves there — 2,182 text matches for "order" become the 92 that claim it; on APIS the tag's members are ADDED to the text matches, never swapped for them. Market tags (payments) and tags almost no company claims are reported and not applied. Set `off` for pure text. The resolution is always echoed as `resolved_tag`.on
try_nowNoOnly providers a developer can start using at no cost right now (free/trial + self-serve/open). (providers only)
industryNo
min_scoreNo
providersNo
onboardingNoAccess model — how to start: open (no key), self-serve, approval. (providers only)
artifact_typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / include
      Added value: +{
      +  "description": "via_provider — also return the APIs of providers whose name matched `q`, the union apis_io_search counts. Needs `q`; adds nothing without one.",
      +  "items": {
      +    "enum": [
      +      "via_provider"
      +    ]
      +  },
      +  "type": "array"
      +}
    • 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."
  2. Changed1 schema field changed
    • addedInput schema / properties / resolve
      Added value: +{
      +  "default": "on",
      +  "description": "When `q` exactly names a tag, apis.io uses it: on PROVIDERS a resource tag (order, webhook, image) replaces the text search with the companies that classify themselves there — 2,182 text matches for \"order\" become the 92 that claim it; on APIS the tag's members are ADDED to the text matches, never swapped for them. Market tags (payments) and tags almost no company claims are reported and not applied. Set `off` for pure text. The resolution is always echoed as `resolved_tag`.",
      +  "enum": [
      +    "on",
      +    "off"
      +  ],
      +  "type": "string"
      +}
  3. 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."
  4. 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"
      +}
  5. Changed4 schema fields changed
    • addedInput schema / properties / onboarding
      Added value: +{
      +  "description": "Access model — how to start: open (no key), self-serve, approval. (providers only)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / pricing
      Added value: +{
      +  "description": "Access model — pricing: free, freemium, free-trial, paid, enterprise. (providers only)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / public
      Added value: +{
      +  "description": "Only providers callable publicly with no signup (onboarding=open). (providers only)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / try_now
      Added value: +{
      +  "description": "Only providers a developer can start using at no cost right now (free/trial + self-serve/open). (providers only)",
      +  "type": "boolean"
      +}
  6. Changed4 schema fields changed
    • addedInput schema / properties / fields / description
      Added value: +"Return exactly these top-level keys (overrides view)."
    • 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"
      +]
    • addedInput schema / properties / view
      Added value: +{
      +  "default": "summary",
      +  "description": "summary (default) returns lean discovery records + *_count for dropped sections; full returns the whole record (use get_api / get_provider for one entity).",
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • addedInput schema / properties / area
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The readOnly annotation already signals safety, and the description adds substantive behavior beyond it: matching is 'LEXICAL', q only searches the API's own name/description, provider-name matches are excluded by default, and meta.query.via_provider reports the added rows. This is genuinely useful non-obvious behavior.

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?

Three dense sentences, front-loaded with purpose, followed by differentiating semantics and routing advice. Every sentence earns its place; there is no filler or repetition of the tool name.

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

Completeness4/5

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

For a read-only, filterable list tool, the description covers core behavior, result-count semantics, and sibling routing. It lacks a general outline of the response shape, but the schema documents view/fields/limit, and the description reveals the key meta field, so the remaining gap is minor.

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

Parameters4/5

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

With 59% schema coverage, the description compensates well by naming the filter families (tag, provider, artifact type, industry, region, rating band) and by clarifying q and include semantics. It does not enrich every undocumented parameter, but it adds meaningful context where the schema is silent or ambiguous.

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 opens with a specific verb and resource: 'Paginated, sortable list of APIs across providers.' It names the filtering dimensions and immediately contrasts itself with apis_io_search, so an agent can distinguish this tool from its closest sibling without inspecting 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?

The description gives explicit routing guidance: 'Use apis_io_search first for a cross-type overview.' It also explains exactly when to pass include=["via_provider"] to match apis_io_search's larger count, turning a likely source of confusion into an actionable choice.

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