Skip to main content
Glama

apis-io

by io.apis
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree text over name + description.
areaNo
bandNoRating bands: exemplar, strong, developing, thin, minimal.
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.
limitNoTop matches to return per section (apis/providers/tags).
matchNoany
regionNo
returnNoReturn only this kind of match. Default: every kind.
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.
industryNo
min_scoreNo
providersNo
artifact_typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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"
+}
  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. 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"
+]
  6. Changed1 schema field changed
    • addedInput schema / properties / area
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral context beyond that: the federated multi-section return, per-section limit semantics, and the disclosure that the `context` parameter is never used in ranking. It does not mention pagination or output format details, but the core behaviors are well disclosed.

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 sentences, front-loaded with 'START HERE' and the core purpose, followed by the routing to alternatives. No wasted words; every sentence carries information an agent needs to select and call the tool correctly.

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 tool with 14 parameters and no output schema, the description adequately explains the return shape (top matches per section with counts) and the main filtering options, and routes to more specific tools for deep dives. It doesn't enumerate all filter values or the full response structure, but for an initial overview tool this is sufficient; an agent can infer the rest from the schema and tool naming.

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 roughly 50% (8 of 14 params documented). The description adds meaning by naming the filter dimensions (tags, artifact types, industry, region, rating band) and clarifying that `limit` is per section, which partially compensates. However, several parameters (area, providers, min_score, industry, artifact_types) are left without explanation in either the schema or description, so the coverage gap is only partially addressed.

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?

States a specific verb ('search') and resource ('APIs.io catalog') and clearly describes the federated overview behavior (returns APIs, providers, tags with counts). It explicitly distinguishes itself from sibling tools find_apis/find_providers/find_tags and get_api/get_provider, making its scope unambiguous.

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?

Opens with 'START HERE' positioning it as the entry point, and explicitly tells the agent when to use alternatives: 'To page/sort the full list of ONE type, use find_apis / find_providers / find_tags; for one entity, get_api / get_provider.' This gives clear routing guidance and conditions.

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

All apis-io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources