Skip to main content
Glama

sendgrid

by io.usefulapi

List email templates

sendgrid_list_templates
Read-only

List your transactional email templates (Dynamic and/or Legacy). Returns { result: [...], _metadata } — use _metadata.next / page_token to paginate. SendGrid: GET /v3/templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNoNumber of templates per page (1–200, default 50).
page_tokenNoPagination token from a previous response's _metadata.
generationsNoWhich template generation(s) to return (default: dynamic).dynamic

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, so the safety profile is covered. The description adds valuable behavior beyond annotations: it discloses the return structure ({ result: [...], _metadata }) and pagination mechanism, which helps the agent understand how to consume results. No contradictions.

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?

Two sentences, front-loaded with the main action, followed by return format and pagination note. Every sentence earns its place with no wasted words.

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

Completeness5/5

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

For a list operation with optional parameters and no output schema, the description provides a complete picture: the resource type, generation filter, return shape, and pagination. The sibling tool context (get_template) further clarifies its role, and the annotations cover safety.

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

Parameters4/5

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

Schema coverage is 100% with each parameter described. The description supplements this by explaining how _metadata.next and page_token relate to pagination, and mentions 'Dynamic and/or Legacy' which aligns with the generations parameter. This adds meaningful usage context beyond the raw schema.

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

Purpose5/5

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

The description clearly states the action: 'List your transactional email templates (Dynamic and/or Legacy)'. It distinguishes from sibling tools like sendgrid_get_template (singular) by conveying a listing operation over multiple templates, and 'transactional email templates' specifies the resource type.

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

Usage Guidelines3/5

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

The description provides context for using the tool (listing templates, paginating via _metadata), but does not explicitly state when to use this tool versus alternatives (e.g., sendgrid_get_template for a single template). It implies usage rather than offering exclusions or alternative recommendations.

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

All sendgrid toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource/action: send mail, manage contacts (upsert/count/search), templates (get/list), suppression lists (bounces/unsubscribes), marketing lists, stats, and health check. No overlaps or ambiguous boundaries.

Naming Consistency5/5

All tools follow a consistent 'sendgrid_' prefix with a verb_noun pattern (e.g., get_template, list_bounces, send_mail). The only minor deviation is 'ping' for health check, but it's a conventional verb-only name and doesn't break the overall consistency.

Tool Count5/5

11 tools is well-scoped for a SendGrid server, covering sending, contacts, templates, suppression, stats, and health. Each tool has a clear purpose and none feel redundant.

Completeness4/5

Core email sending, contact management, and read operations for templates/suppression are covered. However, there are no write operations for templates (create/update/delete) or suppression list management (remove), which are minor gaps that agents can work around by using the existing tools.

Resources