Skip to main content
Glama

Call an approved Scraping Daddy endpoint

api_request

Call any Scraping Daddy ("SD") endpoint and return its response unchanged.

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": {
      "path": "<path>"
    },
    "name": "api_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON request body, for endpoints that take one.
pathYesRelative Scraping Daddy route, e.g. "/v1/tiktok/profile". Must be a known endpoint under /v1 or /v2; full URLs and host overrides are rejected.
methodNoGET or POST. Must be a method the endpoint declares.GET
paramsNoQuery parameters as an object.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"Relative AM-CORE route, e.g. \"/v1/tiktok/profile\". Must be a known\nendpoint under /v1 or /v2; full URLs and host overrides are rejected."New value: +"Relative Scraping Daddy route, e.g. \"/v1/tiktok/profile\". Must be a known\nendpoint under /v1 or /v2; full URLs and host overrides are rejected."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is partly covered, and the description usefully adds that responses are passed through unmodified. It does not disclose auth requirements, whether calls count against a quota, how unknown or disallowed routes fail, or that method must be supported by the chosen endpoint — all relevant for a generic HTTP-calling tool.

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?

One front-loaded sentence with zero filler; the verb, the resource and the return-behavior caveat all land immediately. Nothing is repeated or padded.

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?

An output schema exists so return values need not be explained, and annotations carry part of the behavioral load. However, for a broad generic-passthrough tool sitting beside many specialized siblings, the description is too thin on routing guidance and failure modes to be self-sufficient.

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% and each parameter is documented in the schema, including the path constraint that full URLs and host overrides are rejected. The description adds no parameter-level meaning of its own, which is acceptable given the schema does the work, though it could have noted the GET/POST choice.

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 pairs a specific verb ("Call") with a specific resource ("any Scraping Daddy endpoint") and adds the important property that the response is returned unchanged. It is clear what the tool does but never distinguishes it from the many typed siblings (tiktok_profile, x_tweet, list_endpoints), so an agent cannot tell from the text alone why it would pick the generic passthrough over a dedicated tool.

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 at all. With fifteen sibling tools covering named platforms plus list_endpoints and get_endpoint_schema, the description should say something like "use for endpoints without a dedicated tool" or "use get_endpoint_schema first to learn parameters" — neither is present, leaving routing entirely to inference.

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.