get_unsub_stats
Read-only
Get unsubscribe statistics — unsubscribe rate, top unsubscribed campaigns, and unsubscribe trends.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| campaign_id | No |
xmagnet
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that. However, the description adds no behavioral details beyond the safety profile, such as pagination, rate limits, or how data is scoped. It only lists output content, which is more about purpose than behavior.
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?
The description is two short, focused sentences that immediately state the purpose and key output categories. There is no verbose or redundant wording, and it is appropriately front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and the description captures its core purpose, but the omission of parameter explanations and the absence of an output schema leave the agent under-informed for correct invocation. It is an adequate description for a basic stats tool but not comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage, and the description does not explain the 'limit' or 'campaign_id' parameters. The agent must infer from their names: whether 'limit' applies to the number of top campaigns or trend points, and how 'campaign_id' filters results. The description fails to compensate for the schema gap.
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?
The description clearly specifies the verb 'Get' and the resource 'unsubscribe statistics', and enumerates specific outputs: unsubscribe rate, top unsubscribed campaigns, and unsubscribe trends. This distinguishes it from sibling tools like get_bounce_stats or get_campaign_stats by focusing uniquely on unsubscribe metrics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states what the tool returns but provides no explicit when-to-use guidance or comparison with alternative stats tools. The use case is implied by the name and sibling context, but there is no direct statement about when to choose this over get_bounce_stats or get_campaign_stats.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.4/5.0
Disambiguation2/5
Several tools occupy nearly identical roles (create_contact/add_contacts/save_contacts_to_crm/upload_contacts; add_companies/create_company; search_contacts/search_crm_contacts/find_contacts_at_companies), and the names don't clearly reveal whether they operate on saved or prospected data. Although the descriptions clarify some boundaries, an agent would frequently need to read many descriptions carefully to avoid mis-selection.
Naming Consistency4/5
Most tools follow a snake_case verb_noun pattern such as list_campaigns, create_deal, and update_contact. Minor deviations like company_intelligence, get_icp, load_more_contacts, and the inconsistent use of add_/create_/upload_/save_ for similar creation actions keep it from being fully consistent.
Tool Count1/5
51 tools is far beyond the well-scoped range and exceeds the 50+ extreme threshold. Even for a broad CRM/prospecting/marketing platform, exposing this many tools at once makes agent selection costly and unwieldy.
Completeness2/5
Contact and company creation/read/update are covered, but delete is absent across the board, and campaigns can be drafted, listed, and measured but not edited, activated, paused, or deleted. Deals, forms, and landing pages also lack update/delete lifecycle actions, creating meaningful dead ends for common CRM workflows.