Skip to main content
Glama

bluesky-substack-social-newsletter-scraper-api-mcp

search_endpoints

Read-only

Search 100+ 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.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description does not need to repeat that. It adds useful scope (100+ APIs) and names the fields returned (id, price_usd, p50_ms, summary), but says nothing about result limits, pagination, authentication, or what happens when no filters are supplied.

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 with zero filler; the scope and searchable domains are front-loaded, followed immediately by the return fields. Nothing is buried or redundant.

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

Completeness3/5

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

For a simple two-parameter, read-only search tool, the description covers scope and return shape. It is not complete enough to tell an agent how to combine filters, whether an unfiltered call is permitted, or when to proceed to call_endpoint.

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 coverage is moderate at 50%: the query parameter is described in the schema itself, while category is only an enum with no prose explanation. The description repeats the category values rather than explaining how query and category combine, what happens if either is omitted, or what counts as a valid query.

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 states a specific verb ('Search') and resource ('100+ real-time APIs'), and enumerates the searchable domains. It does not distinguish this from call_endpoint or get_endpoint_schema, so an agent must infer that this is the discovery step rather than invocation or schema lookup.

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 explicit when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as call_endpoint or get_endpoint_schema. Usage is only implied by the word 'Search' and the category list.

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