scrapecreators_age_and_gender
Age and Gender
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to users social profile |
Age and Gender
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to users social profile |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. 'Age and Gender' discloses nothing about side effects, return data, auth requirements, or operational behavior, making this a critical gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is under-specified rather than concise. It is a two-word fragment that provides no functional information, unlike an appropriately sized description that front-loads the essential purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of annotations and output schema, the description is wholly inadequate. It does not explain what data is returned, which social platforms are supported, or how it relates to the many sibling scrapecreators_* tools, making it nearly impossible to select correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides a clear description for the single 'url' parameter ('URL to users social profile'), achieving 100% schema coverage. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Age and Gender' is a tautological restatement of the tool name 'age_and_gender'. It lacks a verb and resource context, and does not distinguish the tool from numerous similar scrapecreators_* sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description contains no context about use cases, prerequisites, or exclusions, leaving the agent without any decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.