scrapecreators_profile_reels
Profile Reels
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Facebook page URL | |
| cursor | No | To paginate through to the next page | |
| next_page_id | No | To paginate through to the next page |
Profile Reels
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Facebook page URL | |
| cursor | No | To paginate through to the next page | |
| next_page_id | No | To paginate through to the next page |
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, but it reveals nothing. It fails to mention what data is returned, pagination behavior, authentication needs, or any side effects, leaving the agent completely in the dark.
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 extremely under-specified. 'Profile Reels' is not a meaningful sentence and does not earn its place; it is a placeholder rather than a concise, informative statement.
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 tool's complexity (3 parameters, no output schema, no annotations), the description is severely inadequate. It does not specify the platform (though the url parameter hints at Facebook), what a 'profile reel' contains, or any expected output, making it impossible for an agent to correctly select and invoke the tool.
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?
Schema description coverage is 100%, so the baseline is 3. The description itself adds zero value beyond the schema; the parameter descriptions for url, cursor, and next_page_id already define their purposes. The tool description does not compensate or clarify anything further.
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 'Profile Reels' is a tautology that merely restates the tool name without specifying any action or resource. It does not say what the tool does or what it returns, making it impossible to distinguish from sibling tools like scrapecreators_reels or scrapecreators_profile_videos.
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?
There is no guidance on when to use this tool vs alternatives. The description provides no context about use cases, prerequisites, or why one would choose this over a sibling tool such as scrapecreators_reels or scrapecreators_profile_videos.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.