Retrieve basic information about campaigns from the Meser10 platform. Use this read-only operation to review campaign details before drafting, sending, or managing messages.
Calls GetCampaignsBasicInfo on the Meser10 platform. Read-only. SOAP operation: GetCampaignsBasicInfo.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full behavioral load. 'Read-only' correctly signals it is a safe, non-mutating call, but with no mention of permissions, pagination, result volume, or response shape for a zero-parameter list operation, disclosure is thin.
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?
Three short sentences with no padding, and the read-only trait appears early. It is concise to the point of being under-informative, though not by verbosity.
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 tool with no annotations and no output schema, the description should say at minimum what record type and fields it returns and roughly how it relates to the many sibling get_* tools. Naming the SOAP operation is not useful to an agent selecting among siblings.
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?
The tool takes no parameters, so there is nothing for the description to document; the empty schema is self-evident and adds no ambiguity. Baseline 4 is appropriate.
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 restates the operation name (GetCampaignsBasicInfo) rather than explaining what a campaign is or what 'basic info' includes. It implies listing campaigns but provides no functional framing, and gives no differentiation from siblings like get_campaign, get_campaign_details, or get_campaign_summary.
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 indication of when to use list_campaigns versus get_campaign, get_campaign_details, get_campaign_summary, or get_campaign_results_by_date. The read-only note is a safety trait, not usage guidance, so an agent has nothing to route on.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.