Skip to main content
Glama
cakemail

Cakemail API MCP Server

Official
by cakemail

cakemail_call_api

Execute any Cakemail API operation by specifying the endpoint path, HTTP method, and optional parameters. Supports GET, POST, PUT, PATCH, DELETE requests.

Instructions

Execute a Cakemail API call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional request body for POST/PUT/PATCH requests
pathYesAPI endpoint path (e.g., "/campaigns/{id}"). Use actual values for path parameters.
methodYesHTTP method (GET, POST, PUT, PATCH, DELETE)
headersNoOptional HTTP headers (e.g., {"Authorization": "Bearer token"})
query_paramsNoOptional query parameters

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention authentication requirements, mutation effects, rate limits, or any side effects of executing API calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (one sentence) but fails to 'earn its place' as it adds no useful information beyond the name. It is under-specified, not efficiently concise.

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?

Despite having an output schema and full parameter documentation, the description is too sparse. It does not explain the tool's role among siblings, preconditions, or operational context, leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions; it does not explain parameter relationships or usage patterns.

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

Purpose2/5

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

The description 'Execute a Cakemail API call' is a tautology of the tool name and does not distinguish this generic API caller from sibling tools like get_endpoint or list_endpoints, which are specific API endpoints. It lacks the verb+resource specificity needed to differentiate.

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

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidelines are provided. The description does not mention when to use this tool versus the sibling tools, nor does it give context on scenarios (e.g., direct API access, unsupported endpoints).

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/cakemail/cakemail-api-documentation-mcp'

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