AnyAPI

Search APIs

search_apis

Read-only

Search APIs by meaning and keyword across name, slug, and description, returning matches WITH their descriptions (schemas omitted), ranked most relevant first. Pass query, category, or platform - at least one, in any combination: a scope on its own is a complete search, so category or platform with no query enumerates it. Add limit to cap matches (default 25, maximum 50). Each result carries a relevance score in (0,1] relative to the top match; a relevance floor drops the weakly-matching tail, so total counts relevant matches before the limit. ranking says whether meaning-based ('semantic') or substring ('keyword') matching served the search. Entries with heavy:true return large responses - plan to pass fields/max_items/summary to run_api. Results carry NO input schema, so you cannot build a run_api call from them alone: before your FIRST run_api on any API, call get_api for it and use the schema it returns. Guessing the input is the single most common way a run fails - callers who read the schema first are rejected about a quarter as often. Use list_apis to browse everything.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	optional cap on matches returned (default 25, maximum 50)
`query`	No	free-text search over API name, slug, and description; optional when category or platform is given
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`category`	No	optional category slug to narrow the search
`platform`	No	optional API slug prefix to narrow the search

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`ranking`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 4, 2026

changedInput schema / properties / query / description

Previous value: -"free-text search over API name, slug, and description"New value: +"free-text search over API name, slug, and description; optional when category or platform is given"

changedInput schema / required

Previous value: -[
-  "query",
-  "context"
-]New value: +[
+  "context"
+]

Changed24 schema fields changedSep 3, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"optional cap on matches returned (default 25); 'total' reports how many relevant matches there were before the cap"New value: +"optional cap on matches returned (default 25, maximum 50)"

addedInput schema / properties / platform

Added value: +{
+  "description": "optional API slug prefix to narrow the search",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "context"
+]

removedOutput schema / properties / ranking / description

Removed value: -"'semantic' when meaning-based ranking served this search, 'keyword' when it fell back to substring matching (relevance is coarser)"

removedOutput schema / properties / results / description

Removed value: -"matching APIs with descriptions (schemas omitted), most relevant first"

removedOutput schema / properties / results / items / properties / baseUsd

Removed value: -{
-  "description": "fixed cost per request in USD, charged regardless of count",
-  "type": "number"
-}

addedOutput schema / properties / results / items / properties / excludesCallerDelay
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / results / items / properties / execution

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "mode": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / failover
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / results / items / properties / heavy / description

Removed value: -"true when this API's responses are typically large; pass fields, max_items, or summary to run_api (and a small limit in the input) to keep the result out of your context"

removedOutput schema / properties / results / items / properties / inputSchema
```
Removed value: -{
-  "description": "normalized input JSON Schema"
-}
```
addedOutput schema / properties / results / items / properties / method
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / results / items / properties / outputSchema
```
Removed value: -{
-  "description": "normalized output JSON Schema"
-}
```
addedOutput schema / properties / results / items / properties / path
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / results / items / properties / perItemUnit

Removed value: -{
-  "description": "the unit perItemUsd is charged per: 'result' (default) or an input unit like 'username' for input-priced SKUs",
-  "type": "string"
-}

removedOutput schema / properties / results / items / properties / perItemUsd

Removed value: -{
-  "description": "marginal cost in USD per billable unit (see perItemUnit); total = baseUsd + perItemUsd × unitCount, capped at priceUsd",
-  "type": "number"
-}

removedOutput schema / properties / results / items / properties / priceUsd

Removed value: -{
-  "description": "maximum price per request in USD (the reserved ceiling at the default limit)",
-  "type": "number"
-}

addedOutput schema / properties / results / items / properties / pricing

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "failoverMaxPer1kUsd": {
+      "type": "number"
+    },
+    "failoverMaxUsd": {
+      "type": "number"
+    },
+    "from": {
+      "additionalProperties": false,
+      "properties": {
+        "baseUsd": {
+          "type": [
+            "null",
+            "number"
+          ]
+        },
+        "maxPer1kUsd": {
+          "type": "number"
+        },
+        "maxUsd": {
+          "type": "number"
+        },
+        "model": {
+          "type": "string"
+        },
+        "perUnitUsd": {
+          "type": [
+            "null",
+            "number"
+          ]
+        },
+        "unit": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "model",
+        "unit",
+        "maxUsd",
+        "maxPer1kUsd"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "from",
+    "failoverMaxUsd",
+    "failoverMaxPer1kUsd"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / provider
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / results / items / properties / relevance / description

Previous value: -"relative relevance in (0,1], 1.0 = the best match in this response; comparable only within this response"New value: +"relative relevance in (0,1], 1.0 = the best match"

changedOutput schema / properties / results / items / required

Previous value: -[
-  "id",
-  "slug",
-  "category",
-  "name",
-  "description",
-  "priceUsd",
-  "baseUsd",
-  "perItemUsd",
-  "relevance"
-]New value: +[
+  "id",
+  "slug",
+  "category",
+  "name",
+  "description",
+  "method",
+  "path",
+  "provider",
+  "execution",
+  "pricing",
+  "failover",
+  "relevance"
+]

removedOutput schema / properties / total / description

Removed value: -"number of relevant matches (after the relevance floor), before the limit cap - if this is large, narrow your query"

Changed8 schema fields changedJul 10, 2026

changedInput schema / properties / limit / description

Previous value: -"optional cap on matches returned (default 25); 'total' reports how many matched before the cap"New value: +"optional cap on matches returned (default 25); 'total' reports how many relevant matches there were before the cap"

addedOutput schema / properties / ranking

Added value: +{
+  "description": "'semantic' when meaning-based ranking served this search, 'keyword' when it fell back to substring matching (relevance is coarser)",
+  "type": "string"
+}

changedOutput schema / properties / results / description

Previous value: -"matching APIs with descriptions (schemas omitted)"New value: +"matching APIs with descriptions (schemas omitted), most relevant first"

addedOutput schema / properties / results / items / properties / heavy

Added value: +{
+  "description": "true when this API's responses are typically large; pass fields, max_items, or summary to run_api (and a small limit in the input) to keep the result out of your context",
+  "type": "boolean"
+}

addedOutput schema / properties / results / items / properties / relevance

Added value: +{
+  "description": "relative relevance in (0,1], 1.0 = the best match in this response; comparable only within this response",
+  "type": "number"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "id",
-  "slug",
-  "category",
-  "name",
-  "description",
-  "priceUsd",
-  "baseUsd",
-  "perItemUsd"
-]New value: +[
+  "id",
+  "slug",
+  "category",
+  "name",
+  "description",
+  "priceUsd",
+  "baseUsd",
+  "perItemUsd",
+  "relevance"
+]

changedOutput schema / properties / total / description

Previous value: -"number of APIs that matched before the limit was applied"New value: +"number of relevant matches (after the relevance floor), before the limit cap - if this is large, narrow your query"

changedOutput schema / required

Previous value: -[
-  "results",
-  "total"
-]New value: +[
+  "results",
+  "total",
+  "ranking"
+]

AddedJun 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Given annotations only indicate readOnly and non-destructive behavior, the description carries the burden of explaining much more. It reveals relevance scoring, relevance floors, total-before-limit counting, ranking type, no input schema in results, heavy:true implications, and the expected first-call schema requirement. No contradiction with annotations.

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

Conciseness4/5

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

The description is front-loaded and dense with useful behavioral guidance. It is somewhat long and includes a somewhat anecdotal rejection-rate warning, but nearly every sentence contributes practical information about output, relevance, heavy responses, or the required get_api follow-up.

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?

For a search tool with no output schema details required, the description is extremely complete. It explains why results are insufficient for run_apis, what to do before first run, how to handle heavy:true entries, and how the tool relates to list_apis and get_api. Nothing essential is missing for an agent to call this tool correctly.

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?

Schema coverage is 100% for basic fields, so the baseline is 3, but the description adds real combinatorial semantics: at least one of query/category/platform, scope-only enumeration, and how limit interacts with relevance/total. It adds substantial meaning beyond the schema, though the context parameter needs no additional explanation.

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 clearly states the tool searches APIs by meaning and keyword across name/slug/description, returns ranked matches with descriptions, and omits schemas. It differentiates itself from siblings like list_apis, get_api, and run_api by describing its exact role and output shape.

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 explicitly says when to use the tool, which parameters must be passed, how categories/platforms work as standalone scopes, and how to combine with limit. It also routes the user to get_api for schemas before run_api and to list_apis for browsing, covering when-not-to-use this tool.

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

All AnyAPI tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct role: discovery (list_apis, search_apis, get_api), pricing (quote_api), execution (run_api), request/result inspection (get_request, read_result), account status (get_balance), and feedback (report_bug, send_feedback). Even the two feedback tools are cleanly separated by defect vs. non-defect.

Naming Consistency5/5

Names consistently follow a snake_case verb_noun pattern: get_api, get_balance, get_request, list_apis, quote_api, read_result, report_bug, run_api, search_apis, send_feedback. There is no mixing of conventions or vague single-word verbs.

Tool Count5/5

Ten tools is well-scoped for an API gateway/aggregator. Each tool covers a necessary phase of the workflow—discovery, schema/pricing inspection, execution, result retrieval, account balance, and user feedback—without redundancy or bloat.

Completeness4/5

The lifecycle from discovering APIs through quoting, executing, checking request status, and reading cached results is well covered. Minor gaps such as no explicit way to cancel a queued/running request or list past requests are workable but not fully closed.

Resources

Need Help?