Skip to main content
Glama

AgentAPIHub — YouTube Transcripts, TikTok, Instagram, Reddit & Hacker News MCP

search_endpoints

Read-only

Search 70+ real-time APIs across x, search, social, commerce, b2b, finance, local, intel. Returns id, price_usd, p50_ms, summary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword (e.g. youtube transcript, tweets, sec filings, seo)
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe read, so the description only needs to add context. It does disclose the result shape (id, price_usd, p50_ms, summary) and the breadth of the catalog, which is useful given no output schema, but it says nothing about result limits, ranking, or pagination for a search over 70+ APIs.

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 short sentences, zero filler, with the catalog scope front-loaded ahead of the return fields. Nothing is wasted or buried.

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 two-parameter, read-only discovery tool with no output schema, the description covers domain breadth and return fields well enough to call it correctly. The main gap is behavioral guidance on result volume and how to use the returned ids, which is minor for a search tool.

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?

The schema already documents query with examples and enumerates all eight category values, covering the more complex parameter. The description's category list merely restates the enum and adds no new meaning such as whether query and category combine, are optional together, or how matching works.

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?

States a specific verb (Search) and resource (70+ real-time APIs) plus the category scope, which clearly separates it from siblings like call_endpoint and get_endpoint_schema that act on a known endpoint. It also lists the return fields, so an agent knows this is a discovery tool. Only the lack of an explicit sibling contrast keeps it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of the sibling tools. An agent must infer from the name alone that this is the discovery step preceding call_endpoint; the description never says so.

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