Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

datasets_creators_item

Read-only

Fetch one stored TikTok creator profile by its exact creator_uid from datasets_creators_search. Deleted and private accounts remain hidden unless include_inactive=true. Hosted MCP always redacts contact email; entitled non-Free REST keys may opt in through the REST item route. Use datasets_creators_search to find creator ids.

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": {
      "creator_uid": "<creator_uid>"
    },
    "name": "datasets_creators_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
creator_uidYesRequired exact creator_uid returned by datasets_creators_search.
include_inactiveNoOptional. Include deleted/private accounts for historical lookup; defaults to false.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Adds real context beyond the readOnlyHint/openWorldHint annotations: deleted and private accounts are hidden by default and only exposed via include_inactive, and contact email is always redacted on hosted MCP with REST-key opt-in. That is exactly the kind of access/visibility behavior an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and constraint, then access caveats. Minor redundancy in restating that ids come from datasets_creators_search at both start and end, but nothing is padded.

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?

With an output schema present, return shape needn't be described, and the description covers the two things that matter for correct invocation: where the id comes from and how inactive/redacted data behaves. Nothing an agent needs 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 coverage is 100% and both parameters are described there, so the schema already carries the load. The description's notes on include_inactive largely restate the schema's 'include deleted/private accounts for historical lookup' and adds no format or edge-case detail, so baseline 3 applies.

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 ('Fetch one stored TikTok creator profile') plus the exact key used ('by its exact creator_uid'), which immediately distinguishes it from the search sibling. An agent knows this is the single-record lookup, not a discovery tool.

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?

Explicitly routes the agent: use datasets_creators_search to find creator ids, then come here with an exact id. It doesn't state negative conditions (e.g. don't use for bulk retrieval), but the prerequisite for the required id is clear enough to select correctly among siblings.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources