census_list_segmentsList audience segments defined in the workspace. Census: GET /segments.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based) for pagination. | |
| per_page | No | Number of records per 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?
Annotations already declare readOnlyHint, so no contradiction. Description adds endpoint info but no extra behavioral context beyond what annotations provide.
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?
Two efficient sentences: purpose and API endpoint. No unnecessary words or repetition.
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?
Simple list tool with pagination; description covers core purpose. Schema covers pagination details. Lacks mention of return format, but acceptable for a straightforward list.
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 coverage is 100%, so parameters are well-described in schema. Description adds no additional meaning to page or per_page.
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?
Clear verb 'list' and resource 'audience segments' with workspace context. Distinct from sibling list tools by naming the resource.
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 on when to use vs. alternatives (e.g., other list tools or search). No prerequisites or exclusions mentioned.
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.
Each tool targets a distinct resource type (destination, model, source, sync, sync run, segment, workspace) with clear get/list/trigger actions. No overlapping purposes; agents can easily distinguish which tool to use for a given operation.
All tools follow a consistent 'census_verb_noun' pattern (e.g., census_get_destination, census_list_syncs). The only action tool, census_trigger_sync, also fits the pattern. No mixing of casing or verb styles.
13 tools is appropriate for a data integration platform that manages multiple resource types (destinations, sources, models, syncs, etc.). It's slightly on the higher side but well-scoped for the domain.
The set covers get, list, and trigger operations, but lacks create, update, and delete for resources. While Census API may not expose mutating operations via MCP, the surface is incomplete for full lifecycle management.