Skip to main content
Glama

douyin-xiaohongshu-rednote-social-scraper-mcp

get_endpoint_schema

Read-only

Get JSON input schema, price, and sample params for an endpoint_id.

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": {
      "endpoint_id": "<endpoint_id>"
    },
    "name": "get_endpoint_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpoint_idYese.g. youtube.video.transcript or search.google.web

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real value by naming the returned payload (JSON input schema, price, sample params), which matters because there is no output schema. It does not cover edge behavior such as unknown endpoint_ids or how pricing units are expressed.

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 short sentence, front-loaded with the verb and the full return payload, with no filler or redundant restatement of the parameter name.

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 single-parameter read tool with no output schema, the description covers the essential gap by stating what comes back. It stops short of describing the response structure or failure modes, which is the only remaining hole.

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 100% and the single parameter already carries concrete examples ('youtube.video.transcript', 'search.google.web') in the schema itself. The description adds no additional meaning about the endpoint_id format or lookup semantics beyond what the schema shows.

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?

Uses a specific verb (Get) and enumerates exactly what is retrieved: JSON input schema, price, and sample params, keyed by endpoint_id. That payload list distinguishes it from call_endpoint (which invokes) and search_endpoints (which discovers), though it never names those siblings explicitly.

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 only implied: the required endpoint_id signals this is a lookup for an endpoint you already know, so discovery via search_endpoints is a logical precursor, but that routing is never stated. No when-not-to-use or prerequisite guidance is given.

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