Facebook Group Posts
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | The URL of the group | |
| cursor | No | The cursor to paginate to the next page | |
| sort_by | No | How to sort the posts | |
| group_id | No | The ID of the group |
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?
No annotations are provided, and the description gives no behavioral details. It does not mention pagination, required parameters, authentication, rate limits, or output behavior, leaving the agent entirely uninformed about the tool's side effects or prerequisites.
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 short, but this is under-specification rather than efficient conciseness. It provides no actionable information and fails to earn its place in a tool definition.
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?
With zero annotations, no output schema, and a two-word description, the tool is severely under-specified. An agent cannot determine what this tool does, how to invoke it correctly, or what the response will look like.
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%, with each parameter having a basic description (e.g., 'The URL of the group'). The description itself adds no parameter semantics beyond the schema, so the baseline score of 3 applies.
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 'Facebook Group Posts' is a noun phrase that merely restates the tool name without a verb or action. It does not specify what the tool does (e.g., scrape, fetch, list) or differentiate it from siblings like scrapecreators_facebook or scrapecreators_subreddit_posts.
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 versus alternatives. Given the large number of sibling scrapecreators tools, the lack of any context for selection is a clear gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.