Skip to main content
Glama

sendgrid

by io.usefulapi

List global unsubscribes

sendgrid_list_global_unsubscribes
Read-only

List globally-unsubscribed email addresses (the global suppression list). Returns an array of { created, email }. SendGrid: GET /v3/suppression/unsubscribes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of records to return.
offsetNoNumber of records to skip (for pagination).
end_timeNoEnd of the time range, as a Unix timestamp (seconds).
start_timeNoStart of the time range, as a Unix timestamp (seconds).

Schema Changelog

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

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations include readOnlyHint=true, covering the safety profile. The description adds valuable context beyond annotations by specifying the return format ('array of { created, email }') and the exact API endpoint. It does not disclose every behavioral detail, but for a read-only listing operation, this is sufficient.

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 two sentences long, front-loaded with the tool's purpose, and includes the return format and endpoint without any superfluous wording. Every sentence earns its place.

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

Completeness4/5

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

For a simple listing tool with no output schema, the description adequately covers the core purpose, return shape, and endpoint. However, it does not explicitly differentiate from the sibling sendgrid_list_bounces, which is a similar listing operation. That missing distinction prevents a perfect score.

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 for all four parameters (limit, offset, end_time, start_time), so the schema already documents each parameter well. The description adds no additional parameter-level meaning beyond what the schema provides, but neither does it need to.

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 tool lists globally-unsubscribed email addresses (the global suppression list), with a specific verb ('List') and resource. It also provides the return shape and the API endpoint, making it unambiguous and distinguishable from sibling tools like sendgrid_list_bounces.

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 does not explicitly state when to use this tool versus alternatives. While the purpose implies it is for global unsubscribes, there is no direct guidance such as 'use this instead of sendgrid_list_bounces' or exclusions. The context is clear but not explicitly differentiated from similar list tools.

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