Skip to main content
Glama
Garoth

SendGrid MCP Server

by Garoth

get_single_send

Retrieve details for a specific email campaign in SendGrid by providing its unique ID to access campaign information.

Instructions

Get details of a specific single send

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
single_send_idYesID of the single send to retrieve

Implementation Reference

  • Handler for the 'get_single_send' tool call. It invokes the SendGrid service to retrieve the single send by ID and returns a formatted JSON response with key details.
    case 'get_single_send':
      const retrievedSingleSend = await service.getSingleSend(args.single_send_id);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            id: retrievedSingleSend.id,
            name: retrievedSingleSend.name,
            status: retrievedSingleSend.status,
            send_at: retrievedSingleSend.send_at,
            list_ids: retrievedSingleSend.send_to.list_ids
          }, null, 2)
        }]
      };
  • Core service method that performs the actual API request to SendGrid to fetch details of a specific single send.
    async getSingleSend(singleSendId: string): Promise<SendGridSingleSend> {
      const [response] = await this.client.request({
        method: 'GET',
        url: `/v3/marketing/singlesends/${singleSendId}`
      });
      return response.body as SendGridSingleSend;
    }
  • Input schema definition for the 'get_single_send' tool, specifying the required 'single_send_id' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        single_send_id: {
          type: 'string',
          description: 'ID of the single send to retrieve'
        }
      },
      required: ['single_send_id']
    }
  • Registration of the 'get_single_send' tool within the getToolDefinitions array, including name, description, and input schema.
    {
      name: 'get_single_send',
      description: 'Get details of a specific single send',
      inputSchema: {
        type: 'object',
        properties: {
          single_send_id: {
            type: 'string',
            description: 'ID of the single send to retrieve'
          }
        },
        required: ['single_send_id']
      }
    },
Behavior2/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 states it retrieves details but doesn't specify what details are included, whether it's a read-only operation, error handling for invalid IDs, or any rate limits. This is a significant gap for a tool that likely interacts with external data.

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 a single, direct sentence that efficiently conveys the core purpose without unnecessary words. It is front-loaded and appropriately sized for a simple retrieval tool, earning full marks for conciseness.

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?

Given the complexity of retrieving specific data with no annotations or output schema, the description is incomplete. It doesn't explain what 'details' include, potential errors, or the return format, leaving the agent under-informed for proper usage in a context with many sibling tools.

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?

The input schema has 100% description coverage, clearly documenting the single required parameter 'single_send_id'. The description adds no additional meaning beyond this, such as format examples or sourcing hints, so it meets the baseline for high schema coverage without compensating value.

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 clearly states the action ('Get details') and resource ('a specific single send'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'list_single_sends' or 'get_template', which would require mentioning it retrieves detailed metadata for a single identified send rather than listing multiple sends or retrieving templates.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'list_single_sends' for listing sends or 'get_template' for template details, nor does it specify prerequisites such as needing a valid single_send_id. This leaves the agent without context for tool selection.

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/Garoth/sendgrid-mcp'

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