Skip to main content
Glama
deyikong

SendGrid MCP Server

by deyikong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Contacts

search_contacts
Read-onlyIdempotent

Search contacts by query conditions to find matching recipients without creating a segment. Returns up to 50 results without pagination.

Instructions

Search for contacts using query conditions without creating a segment. Only the first 50 matching contacts are returned — this endpoint does not support pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query using segment conditions (e.g., 'email LIKE "@example.com"')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / page_size
      Removed value: -{
-  "default": 50,
-  "description": "Number of results to return (max 100)",
-  "type": "number"
-}
    • removedInput schema / properties / page_token
      Removed value: -{
-  "description": "Token for pagination",
-  "type": "string"
-}
  2. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that the operation is read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond those annotations: it does not create a segment, only returns the first 50 matches, and has no pagination. This is valuable for agents deciding whether partial results are acceptable.

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 compact sentences with no redundancy. The core purpose is front-loaded, the side-effect boundary ('without creating a segment') is explicit, and the critical result limit is stated last without sacrificing clarity.

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 simple one-parameter, read-only search tool, the description covers the operation, the query condition requirement, the no-segment side effect, and the result cap. No output schema exists, but the description still communicates that matching contacts are returned, which is sufficient for correct invocation.

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 for the sole parameter is 100%, so the schema already fully documents 'query' with an example. The description's 'query conditions' phrasing is consistent with, but does not add meaningful detail beyond, the parameter schema. Baseline 3 is appropriate.

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 identifies a specific action ('Search for contacts'), a specific resource ('contacts'), and a defining constraint ('using query conditions without creating a segment'). This clearly differentiates it from segment-creation workflows and from other contact-retrieval tools by emphasizing query-condition matching.

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 implies when to use the tool: when you need ad-hoc contact search via query conditions and do not want to create a segment. It also provides an important limits-related caveat (first 50 results, no pagination). However, it does not explicitly name alternatives such as search_contacts_by_emails or list_contacts, nor does it state when those should be preferred.

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

Deploy Server

Other Tools