Skip to main content
Glama

FlowCastle

by ai.flowcastle
OverviewDiscussionsAdmin

list_contacts

Read-only

List and search contacts in the application, paginated, newest first. Read-only. Filters combine as AND; search matches name, username, email, phone, and platformId; tags / tagIds keep only contacts carrying at least one of those tags (UTM attribution tags are named "utm: " — discover them with list_contact_tags). total is the full match count, so limit: 1 counts an audience cheaply. Returns compact contact summaries without variable values — use get_contact for one contact's variables. Remember platformId is unique only per bot, so the same person talking to two bots appears as two contacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number. Defaults to 1.
tagsNoOnly contacts carrying at least one of these tags, by exact tag name (case-insensitive), e.g. ["utm: tgads_official_0905"]. A name no contact in scope carries is an error listing what is missing. Combine with tagIds (union).
botIdNoOnly contacts belonging to this bot (must be one of the application's bots). Omit for all bots in the application.
limitNoContacts per page, between 1 and 100. Defaults to 20.
searchNoCase-insensitive substring matched against first/last name, username, email, phone, and platformId. Omit to list without searching.
statusNoOnly contacts with this subscription status ("subscribed" or "unsubscribed"). Omit for both.
tagIdsNoSame as `tags`, by tag id (from list_contact_tags).
isActiveNoTrue for active contacts only, false for deactivated only. Omit for both.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / botId / description
      Previous value: -"Only contacts belonging to this bot. Omit for all bots in the application."New value: +"Only contacts belonging to this bot (must be one of the application's bots). Omit for all bots in the application."
    • addedInput schema / properties / tagIds
      Added value: +{
+  "description": "Same as `tags`, by tag id (from list_contact_tags).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Only contacts carrying at least one of these tags, by exact tag name (case-insensitive), e.g. [\"utm: tgads_official_0905\"]. A name no contact in scope carries is an error listing what is missing. Combine with tagIds (union).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'Read-only' is consistent with them. Beyond annotations, it discloses filter combination semantics (AND), tag union behavior, total-count semantics for cheap counting, compact return shape, and the platformId-per-bot data model quirk. No contradiction with annotations.

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?

Five dense sentences, each earning its place: purpose/ordering, safety, filter semantics with tag guidance, counting trick, and return-shape routing plus a data-model caveat. The most important facts are front-loaded and there is no repetition of schema content.

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 9-parameter tool with no output schema, the description covers every decision point: scope, ordering, filter composition, search fields, tag naming convention, return semantics, and sibling routing. The compact-summary and total notes partially compensate for the missing output schema. Nothing an agent needs to invoke it correctly is missing.

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%, so the baseline is 3. The description adds cross-cutting meaning the schema does not convey: filters combine as AND, search matches the listed fields, tags/tagIds form a union, and platformId is unique only per bot. This is genuine value beyond the per-parameter schema descriptions, though it deliberately does not re-describe each parameter.

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?

Opens with a specific verb+resource: 'List and search contacts in the application, paginated, newest first.' It names scope, ordering, and pagination, which distinguishes it from get_contact (single contact), list_contact_tags (tags only), and the create/update contact mutations. The 'Read-only' qualifier further separates it from mutation siblings.

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?

Provides explicit routing to alternatives: 'use get_contact for one contact's variables' and 'discover them with list_contact_tags' for UTM tag names. The 'limit: 1 counts an audience cheaply' tip gives concrete when-to-use guidance, and the platformId-per-bot caveat tells agents when results will differ from their expectations. Clear context with named siblings.

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

All FlowCastle 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