scrapingdog-mcp

Overview Schema Source Related Servers Discussions Admin

x_profile

Fetch a public X (Twitter) profile's name, handle, bio, and follower counts as JSON by providing a username or user ID.

Instructions

Scrape an X (Twitter) profile via Scrapingdog (/x/profile). Returns the profile's name, handle, follower counts, bio, and other public metadata as JSON. Pass a username or user 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": {
      "profileId": "<profileId>"
    },
    "name": "x_profile"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No	Override the configured Scrapingdog API key for this call. If omitted, the key is read from SCRAPINGDOG_API_KEY or a local .env file.
`profileId`	Yes	The user ID or username of the X profile to scrape, e.g. 'elonmusk' or 'nasa'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 31, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states that it returns JSON with specific fields, but it does not mention the dependency on Scrapingdog API key, rate limits, caching behavior, or whether it performs a live scrape. These are significant omissions for an external scraping 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?

The description is two sentences, front-loaded with the action and endpoint, and contains no filler. Every word contributes to understanding the tool's function.

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 simple read-only scrape with only two parameters, the description adequately covers purpose, input format, and return fields. However, it omits mention of API key requirements or error conditions, and with no output schema, it relies on the listed fields to convey the response shape. Still, it provides enough context for an agent to select and invoke the tool correctly in most cases.

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 description coverage is 100%, so baseline 3 applies. The description restates that the tool accepts a username or user ID, which is already in the schema's profileId description. It adds no new semantic detail beyond what the schema already documents.

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

Purpose5/5

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

The description uses a specific verb 'Scrape' with a clear resource 'X (Twitter) profile' and even names the endpoint '/x/profile'. It distinguishes the tool from siblings like x_post and search tools by focusing on profile metadata.

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?

The description provides a parameter-level instruction ('Pass a username or user ID') but gives no explicit guidance on when to use this tool versus alternatives. The use case is implied by the resource, but no exclusions or comparisons with sibling tools are offered.

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

Deploy Server