Skip to main content
Glama
Sign In

API.SH

by sh.api
OverviewDiscussionsAdmin

search_apis

Read-only

Search the API.SH catalog of endpoints by keyword (site, data type, route) and optional category. Returns routes, what they return, required parameters and credit price.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 15).
queryYesKeywords, e.g. 'tiktok comments' or 'zillow'
categoryNoOptional category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "social",
-  "e-commerce",
-  "real estate",
-  "search & seo",
-  "travel & events",
-  "jobs & b2b",
-  "media & music",
-  "ad libraries",
-  "creator tools",
-  "web data",
-  "ai answers",
-  "reference",
-  "finance & crypto",
-  "automotive",
-  "content & communities",
-  "logistics",
-  "education",
-  "sports",
-  "public data",
-  "government & registries",
-  "news",
-  "local services",
-  "food & delivery",
-  "other"
-]New value: +[
+  "social",
+  "e-commerce",
+  "real estate",
+  "search & seo",
+  "travel & events",
+  "jobs & b2b",
+  "media & music",
+  "ad libraries",
+  "creator tools",
+  "web data",
+  "ai answers",
+  "reference",
+  "finance & crypto",
+  "automotive",
+  "content & communities",
+  "logistics",
+  "education",
+  "sports",
+  "public data",
+  "government & registries",
+  "news",
+  "local services",
+  "food & delivery"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "social",
-  "e-commerce",
-  "real estate",
-  "search & seo",
-  "travel & events",
-  "jobs & b2b",
-  "media & music",
-  "ad libraries",
-  "creator tools",
-  "web data",
-  "ai answers",
-  "reference",
-  "finance & crypto",
-  "automotive",
-  "content & communities",
-  "logistics",
-  "education",
-  "sports",
-  "public data",
-  "government & registries",
-  "news",
-  "local services",
-  "food & delivery"
-]New value: +[
+  "social",
+  "e-commerce",
+  "real estate",
+  "search & seo",
+  "travel & events",
+  "jobs & b2b",
+  "media & music",
+  "ad libraries",
+  "creator tools",
+  "web data",
+  "ai answers",
+  "reference",
+  "finance & crypto",
+  "automotive",
+  "content & communities",
+  "logistics",
+  "education",
+  "sports",
+  "public data",
+  "government & registries",
+  "news",
+  "local services",
+  "food & delivery",
+  "other"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "social",
-  "e-commerce",
-  "real estate",
-  "search & seo",
-  "travel & events",
-  "jobs & b2b",
-  "media & music",
-  "ad libraries",
-  "creator tools",
-  "web data",
-  "ai answers",
-  "reference",
-  "finance & crypto",
-  "automotive",
-  "content & communities",
-  "logistics",
-  "education",
-  "sports",
-  "public data",
-  "government & registries",
-  "news",
-  "local services",
-  "food & delivery",
-  "other"
-]New value: +[
+  "social",
+  "e-commerce",
+  "real estate",
+  "search & seo",
+  "travel & events",
+  "jobs & b2b",
+  "media & music",
+  "ad libraries",
+  "creator tools",
+  "web data",
+  "ai answers",
+  "reference",
+  "finance & crypto",
+  "automotive",
+  "content & communities",
+  "logistics",
+  "education",
+  "sports",
+  "public data",
+  "government & registries",
+  "news",
+  "local services",
+  "food & delivery"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "social",
-  "e-commerce",
-  "real estate",
-  "search & seo",
-  "travel & events",
-  "jobs & b2b",
-  "media & music",
-  "ad libraries",
-  "creator tools",
-  "web data",
-  "ai answers",
-  "reference",
-  "finance & crypto",
-  "automotive",
-  "content & communities",
-  "logistics",
-  "education",
-  "sports",
-  "public data",
-  "government & registries",
-  "news",
-  "local services",
-  "food & delivery"
-]New value: +[
+  "social",
+  "e-commerce",
+  "real estate",
+  "search & seo",
+  "travel & events",
+  "jobs & b2b",
+  "media & music",
+  "ad libraries",
+  "creator tools",
+  "web data",
+  "ai answers",
+  "reference",
+  "finance & crypto",
+  "automotive",
+  "content & communities",
+  "logistics",
+  "education",
+  "sports",
+  "public data",
+  "government & registries",
+  "news",
+  "local services",
+  "food & delivery",
+  "other"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "social",
-  "e-commerce",
-  "real estate",
-  "search & seo",
-  "travel & events",
-  "jobs & b2b",
-  "media & music",
-  "ad libraries",
-  "creator tools",
-  "web data",
-  "ai answers",
-  "reference",
-  "finance & crypto",
-  "automotive",
-  "content & communities",
-  "logistics",
-  "education",
-  "sports",
-  "public data",
-  "government & registries",
-  "news",
-  "local services",
-  "food & delivery",
-  "other"
-]New value: +[
+  "social",
+  "e-commerce",
+  "real estate",
+  "search & seo",
+  "travel & events",
+  "jobs & b2b",
+  "media & music",
+  "ad libraries",
+  "creator tools",
+  "web data",
+  "ai answers",
+  "reference",
+  "finance & crypto",
+  "automotive",
+  "content & communities",
+  "logistics",
+  "education",
+  "sports",
+  "public data",
+  "government & registries",
+  "news",
+  "local services",
+  "food & delivery"
+]
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, closed-world read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description is not obligated to restate safety. It does add genuine behavioral value by disclosing what comes back — routes, their outputs, required parameters, and credit price — which tells the agent the result is rich enough to drive a subsequent call_api invocation.

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?

Two sentences, front-loaded with the verb and resource, then the return payload. No filler, no repetition of the parameter list beyond what clarifies the search facets.

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?

With no output schema, the description correctly compensates by listing the returned fields, and all three parameters are covered. Minor gaps remain: no mention of pagination/result limits beyond the limit param, ranking behavior, or that the returned routes are consumed via call_api.

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 description coverage is 100%, so the schema already documents query, category, and limit. The description still adds meaning by characterizing query keywords as site, data type, or route facets, which frames how to compose a search that the schema's bare examples ('tiktok comments', 'zillow') do not fully convey.

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

Purpose4/5

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

The description names a specific verb and resource ("Search the API.SH catalog of endpoints") and scopes the search inputs to keyword and optional category. It is clearly distinguishable from sibling tools like get_endpoint or call_api, though it never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the discovery step before calling call_api or get_endpoint, but the description gives no explicit when-to-use, when-not-to-use, or alternative routing guidance. No prerequisites or exclusions are mentioned.

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

All API.SH 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