Skip to main content
Glama
mundurragacl

Amazon Connect MCP Server

by mundurragacl

campaigns_pause

Pause an active Amazon Connect campaign by providing its campaign ID.

Instructions

Pause a campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description provides no behavioral information beyond the literal action. There are no annotations, so the description carries the full burden, but it does not disclose side effects, reversibility, required permissions, or effects on ongoing campaign activity. This is a severe transparency gap.

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 exceptionally concise at three words, front-loaded, and contains no filler. It earns a perfect score for brevity and clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is extremely minimal and does not provide context about the tool's lifecycle position, prerequisites, or relationship to sibling campaign tools. While the operation is simple, the lack of annotations and usage guidance makes the description insufficient for an agent to fully understand when and how to use it correctly.

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 schema has one required parameter, campaign_id, but the description does not mention or explain it. With 0% schema description coverage, the description fails to compensate for the lack of parameter meaning, leaving the agent to infer that the campaign_id is the target of the pause.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Pause a campaign' clearly states the action (pause) and the resource (campaign), distinguishing it from siblings like campaigns_start, campaigns_resume, and campaigns_stop. It is not a pure tautology because it converts the name into a grammatically complete sentence, but it lacks any additional scope or differentiation beyond the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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. The description does not mention prerequisites, when pausing is appropriate compared to stopping or resuming, or reference any sibling tools. The agent receives no contextual direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mundurragacl/amazon-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server