Skip to main content
Glama

Search contacts

search_contacts
Read-only

List and search this workspace's contacts, filtered by company/owner/tag, sorted and paginated. Returns summary rows (id, firstName, lastName, email, phone, jobTitle, company, owner, tags) plus pagination { page, perPage, total }. Use get_contact to fetch one contact's full detail by id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search over name, email and company. Omit for no text filter.
tagNoFilter to contacts carrying this tag. Omit for any tag.
pageNo1-based page number of results to return. Default 1.
sortByNoField to sort by. Default name. Allowed: name, email, createdAt.name
ownerIdNoFilter to contacts owned by this workspace member's user id.
perPageNoNumber of contacts per page (1-100). Default 25.
sortDirNoSort direction. Default asc.asc
companyIdNoFilter to contacts at this company id (from search_companies).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed8 schema fields changed
    • addedInput schema / properties / companyId / description
      Added value: +"Filter to contacts at this company id (from search_companies)."
    • addedInput schema / properties / ownerId / description
      Added value: +"Filter to contacts owned by this workspace member's user id."
    • addedInput schema / properties / page / description
      Added value: +"1-based page number of results to return. Default 1."
    • addedInput schema / properties / perPage / description
      Added value: +"Number of contacts per page (1-100). Default 25."
    • addedInput schema / properties / q / description
      Added value: +"Free-text search over name, email and company. Omit for no text filter."
    • addedInput schema / properties / sortBy / description
      Added value: +"Field to sort by. Default name. Allowed: name, email, createdAt."
    • addedInput schema / properties / sortDir / description
      Added value: +"Sort direction. Default asc."
    • addedInput schema / properties / tag / description
      Added value: +"Filter to contacts carrying this tag. Omit for any tag."
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true and destructiveHint=false, so the agent knows it is a safe read operation. The description adds the exact summary row fields (id, firstName, lastName, etc.) and pagination structure, which is useful behavioral context beyond the annotations. However, it does not disclose potential performance characteristics or search semantics.

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?

Three sentences, front-loaded with purpose, then return format, then sibling guidance. No redundant information and every sentence adds value.

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?

Given the schema already covers parameters, the description adequately explains the return format (summary rows + pagination) and provides an alternative for full details. It is complete for a read-only list/search tool with no output schema.

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 description coverage is 100%, so parameter semantics are fully documented in the schema. The description adds a high-level grouping (filter by company/owner/tag, sorted/paginated) which maps to parameters but does not explain individual parameter syntax or constraints. 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 clearly states it lists/searches workspace contacts with filtering by company/owner/tag, sorting, and pagination. It distinguishes from get_contact by noting 'Use get_contact to fetch one contact's full detail by id.'

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

Usage Guidelines5/5

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

It explicitly directs the agent to use get_contact when full detail is needed, providing an explicit alternative. This gives clear when-to-use and when-not-to-use guidance for at least one relevant sibling tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources