Skip to main content
Glama
Sign In

Inboxapp

by com.inboxapp.mcp
OverviewDiscussionsAdmin

Find contacts

contacts_list
Read-onlyIdempotent

Find contacts

Finds contacts by the platform identity of one of their profiles: a platform with platformId or username.

Input Schema

NameRequiredDescriptionDefault
qNoSearches contact and profile names, usernames, emails and phone numbers. Not combinable with `platformId` or `username`. Results follow `createdAt`, not relevance, and can trail changes by a few seconds.
limitNoPage size, from 1 to 100. Defaults to 50.
cursorNoThe previous page's `nextCursor`. Opaque, and valid only with the filters it was issued for.
expandNoRelated resources to embed next to their ID field, one path per key, at most 4.
platformNoContacts with a profile on these platforms. Defaults to every platform available to the team. `platformId` needs exactly one. Repeat the key to match any of several.
usernameNoContacts with a profile of this username, without its display prefix. One username may match several contacts. Give one of `platformId`, `username` or `q`, repeating the key for up to 100. No match is an empty page.
platformIdNoContacts with a profile of this platform ID. Give one of `platformId`, `username` or `q`, repeating the key for up to 100. No match is an empty page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $defs / Platform / description
      Previous value: -"The platform. Every team can use twitter, linkedin; a team may have others enabled."New value: +"The platform. Every team can use twitter, linkedin, whatsapp; a team may have others enabled."
    • changedInput schema / $defs / Platform / examples
      Previous value: -[
-  "twitter",
-  "linkedin"
-]New value: +[
+  "twitter",
+  "linkedin",
+  "whatsapp"
+]
  2. Changed2 schema fields changed
    • changedInput schema / $defs / Platform / description
      Previous value: -"The platform. Every team can use twitter; a team may have others enabled."New value: +"The platform. Every team can use twitter, linkedin; a team may have others enabled."
    • changedInput schema / $defs / Platform / examples
      Previous value: -[
-  "twitter"
-]New value: +[
+  "twitter",
+  "linkedin"
+]
  3. Changed8 schema fields changed
    • removedInput schema / properties / platform / $ref
      Removed value: -"#/$defs/Platform"
    • addedInput schema / properties / platform / description
      Added value: +"Contacts with a profile on these platforms. Defaults to every platform available to the team. `platformId` needs exactly one. Repeat the key to match any of several."
    • addedInput schema / properties / platform / items
      Added value: +{
+  "$ref": "#/$defs/Platform"
+}
    • changedInput schema / properties / platform / type
      Previous value: -"string"New value: +"array"
    • changedInput schema / properties / platformId / description
      Previous value: -"Contacts with a profile of this platform ID. Give this or the other identity filter, repeating the key for up to 100. No match is an empty page."New value: +"Contacts with a profile of this platform ID. Give one of `platformId`, `username` or `q`, repeating the key for up to 100. No match is an empty page."
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Searches contact and profile names, usernames, emails and phone numbers. Not combinable with `platformId` or `username`. Results follow `createdAt`, not relevance, and can trail changes by a few seconds.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / username / description
      Previous value: -"Contacts with a profile of this username, without its display prefix. One username may match several contacts. Give this or the other identity filter, repeating the key for up to 100. No match is an empty page."New value: +"Contacts with a profile of this username, without its display prefix. One username may match several contacts. Give one of `platformId`, `username` or `q`, repeating the key for up to 100. No match is an empty page."
    • changedInput schema / required
      Previous value: -[
-  "platform"
-]New value: +[]
  4. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that — no note about empty-result behavior, result ordering by `createdAt`, index lag, or cursor scoping, all of which are behavioral facts relevant to callers and which appear only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, with the identifying filter named immediately. The opening line simply repeats the title and tool name, which is wasted space, but the remaining sentence is efficient.

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?

For a 7-parameter search tool with a rich schema, no output schema, and a near-identical sibling in `people_search`, the description should carry the routing burden — and it does not. An agent cannot tell from this text when to prefer `contacts_list` over `people_search`, nor that plain name/email lookup is even possible here.

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 the baseline is 3 and the parameters are fully self-documenting. The description only restates `platform`/`platformId`/`username` and omits `q`, `limit`, `cursor` and `expand` entirely, so it adds no meaning beyond the schema and slightly skews the picture of what the tool accepts.

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

Purpose3/5

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

The verb+resource is clear ("Finds contacts"), but the stated scope — "by the platform identity of one of their profiles" — is narrower than the schema, which also supports free-text `q` across names, usernames, emails and phone numbers. It also does nothing to separate this from the sibling `people_search`, which an agent would naturally consider for the same job.

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 implies a minimum filter ("a `platform` with `platformId` or `username`") but gives no explicit when-to-use, when-not, or alternative. There is no mention of `people_search`, no note that `q` is mutually exclusive with the identity filters (that lives only in the schema), and no guidance on paging with `cursor`.

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

All Inboxapp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources