List audience contacts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size, maximum 100 | |
| cursor | No | Opaque pagination cursor | |
| audience_id | Yes | Audience ID | |
| organization_id | Yes | Active organization ID |
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, the description carries the full burden of behavioral disclosure. It only says 'List audience contacts' and does not reveal pagination behavior, return format, ordering, or that this is a read-only operation. Minimal value is added beyond the tool name.
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 and free of fluff, but it is under-specified. It earns its place but does not provide enough useful content to be considered well-structured for an agent.
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?
For a list endpoint with required organization_id and audience_id, pagination parameters, and no output schema or annotations, the description is too thin. It does not mention pagination, what contacts are returned, or any practical invocation context.
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 schema fully documents the four parameters. The description adds no additional semantic detail, but this is acceptable given the baseline of 3 when the schema handles parameter documentation.
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 'List audience contacts' uses a specific verb and resource, clearly distinguishing it from sibling tools like audience_create or audience_delete. It is somewhat generic compared to audience_member_add/remove, but the intent is clear.
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 such as commsharbor_audiences or commsharbor_audience_get. The description simply states the function without any context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most resource CRUD sets are distinct, but the server duplicates entire CRM activity/task tool groups under crm_* and platform_crm_* with identical descriptions, so an agent cannot tell which set to call. Additional overlap exists around identity/context (me, context, platform_context, organizations) and exports (contacts_export vs data_export_create).
Names generally follow commsharbor_<resource>_<action>, but list endpoints are split between plural nouns (audiences, webhooks) and *_list suffixes (crm_activities_list), and some tools use bare nouns or verbs (health, me, context, logout). The mixed conventions are readable but not fully predictable.
141 tools is far beyond a coherent surface for an agent to select from. Even with a broad CRM/email platform scope, the set should be consolidated, namespaced more aggressively, or split into multiple focused servers.
Coverage is broad: campaigns, templates, audiences, CRM objects, imports/exports, auth, billing, domains, webhooks, and suppressions all have lifecycle tools. Gaps like suppression deletion, webhook update, and a non-platform leads group are minor relative to the overall surface, though the duplicate platform sets muddy completeness.