ScrapeCreators MCP Server

Search Users

threads_search_users

Search Threads users by username to find matching profiles and account IDs before fetching their profile or posts. Requires confirm=true for paid API calls.

Instructions

Searches for Threads users by username, returning matching profiles with username, full_name, profile_pic_url, is_verified, and pk. Useful for finding user accounts before fetching their profile or posts. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

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": {
      "query": "<query>"
    },
    "name": "threads_search_users"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Username to search for
`account`	No	Named private ScrapeCreators account; selects credentials, not a remote account ID.
`confirm`	No	Must be true for the specific approved credit-consuming research call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations flag readOnlyHint=false but destructiveHint=false; the description reconciles that tension by stating read-like POSTs don't publish to social platforms, and adds two traits not in the annotations: paid credit consumption and the confirm=true gate. Remaining gaps are minor (no rate-limit or pagination detail).

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?

Three tight sentences, front-loaded with purpose followed by usage context and then the cost/confirm constraint. With no output schema, the field enumeration earns its place rather than being filler.

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

Completeness5/5

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

For a 3-param search tool with no output schema, the description covers return shape, intended usage, credit cost, and the confirm flag. Nothing an agent needs to invoke it correctly is missing.

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 all three parameters (query, account, confirm) are already documented in the schema, including the credential-vs-remote-account nuance of 'account'. The description only restates the confirm requirement without adding format or syntax detail, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Searches for Threads users by username') and enumerates the returned fields, distinguishing it from the domain's keyword search sibling (threads_search_by_keyword). An agent can tell what it does without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear workflow context ('finding user accounts before fetching their profile or posts'), which tells the agent when this is the right starting point. It stops short of naming the alternative (threads_search_by_keyword) or stating when-not-to-use, so no explicit routing.

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

Deploy Server