Skip to main content
Glama

callingly

by com.callingly
OverviewDiscussionsAdmin

Look up values in a connected CRM

get_crm_options
Read-only

Fetch live lists from a connected CRM — its fields, tags, users, pipeline stages, Facebook pages/forms, Follow Up Boss inboxes or Follow Up Boss ponds — so their ids can be passed to update_integration (field mapping, routing triggers and tag rules, settings, user mapping) or manage_user (CRM user links). Supported: fields (ActiveCampaign, Brivity, CINC, Follow Up Boss, GoHighLevel, HubSpot, Keap, Lofty, Pipedrive, Realtor.com, Salesforce, Wise Agent); tags (ActiveCampaign, CINC, Keap, Wise Agent); users (ActiveCampaign, Aircall, Brivity, CINC, Follow Up Boss, GoHighLevel, HubSpot, Keap, Lofty, Pipedrive, Salesforce, Wise Agent); stages (Pipedrive); pages and forms (Facebook); inboxes (Follow Up Boss Inbox App); ponds (Follow Up Boss). Calls the CRM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhat to list. fields: CRM field keys for the field mapping. tags: tags (Wise Agent: categories; CINC: labels). users: CRM users, to link to Callingly users. stages: Pipedrive stages. pages / forms: Facebook pages and the connected page's lead forms. inboxes: Follow Up Boss team inboxes. ponds: Follow Up Boss ponds.
searchNoOnly options whose name or id contains this text (case-insensitive). Lists are capped at 200.
platformNoInstead of integration_id: use the account's connected integration of this platform, as the dashboard's per-platform lists do.
object_typeNoSalesforce fields only: the object to describe (Lead, Contact, Opportunity or a custom object API name). Defaults to the integration's object.
reference_toNoSalesforce fields only: just the lookup fields that point at this object, e.g. "User" for the lead owner field (settings.owner_field).
integration_idNoThe integration to ask, from get_integrations. Required for ActiveCampaign, Facebook and Keap, Pipedrive stages and Salesforce fields; otherwise platform is enough.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"What to list. fields: CRM field keys for the field mapping. tags: tags (Wise Agent: categories; CINC: labels). users: CRM users, to link to Callingly users. stages: Pipedrive stages. pages / forms: Facebook pages and the connected page's lead forms. inboxes: Follow Up Boss team inboxes."New value: +"What to list. fields: CRM field keys for the field mapping. tags: tags (Wise Agent: categories; CINC: labels). users: CRM users, to link to Callingly users. stages: Pipedrive stages. pages / forms: Facebook pages and the connected page's lead forms. inboxes: Follow Up Boss team inboxes. ponds: Follow Up Boss ponds."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "fields",
-  "tags",
-  "users",
-  "stages",
-  "pages",
-  "forms",
-  "inboxes"
-]New value: +[
+  "fields",
+  "tags",
+  "users",
+  "stages",
+  "pages",
+  "forms",
+  "inboxes",
+  "ponds"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / integration_id / description
      Previous value: -"The integration to ask, from get_integrations. Required for ActiveCampaign, Drip, Facebook and Keap, Pipedrive stages and Salesforce fields; otherwise platform is enough."New value: +"The integration to ask, from get_integrations. Required for ActiveCampaign, Facebook and Keap, Pipedrive stages and Salesforce fields; otherwise platform is enough."
    • changedInput schema / properties / kind / description
      Previous value: -"What to list. fields: CRM field keys for the field mapping. tags: tags (Wise Agent: categories; CINC: labels). users: CRM users, to link to Callingly users. stages: Pipedrive stages. events: Drip events. pages / forms: Facebook pages and the connected page's lead forms. inboxes: Follow Up Boss team inboxes."New value: +"What to list. fields: CRM field keys for the field mapping. tags: tags (Wise Agent: categories; CINC: labels). users: CRM users, to link to Callingly users. stages: Pipedrive stages. pages / forms: Facebook pages and the connected page's lead forms. inboxes: Follow Up Boss team inboxes."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "fields",
-  "tags",
-  "users",
-  "stages",
-  "events",
-  "pages",
-  "forms",
-  "inboxes"
-]New value: +[
+  "fields",
+  "tags",
+  "users",
+  "stages",
+  "pages",
+  "forms",
+  "inboxes"
+]
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "activecampaign",
-  "aircall",
-  "brivity",
-  "cinc",
-  "drip",
-  "facebook",
-  "followupboss",
-  "followupboss-inboxapp",
-  "gohighlevel",
-  "hubspot",
-  "keap",
-  "lofty",
-  "pipedrive",
-  "realtor",
-  "salesforce",
-  "wiseagent"
-]New value: +[
+  "activecampaign",
+  "aircall",
+  "brivity",
+  "cinc",
+  "facebook",
+  "followupboss",
+  "followupboss-inboxapp",
+  "gohighlevel",
+  "hubspot",
+  "keap",
+  "lofty",
+  "pipedrive",
+  "realtor",
+  "salesforce",
+  "wiseagent"
+]
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the bar is lower. The description adds real context beyond that: results are live-fetched from the external CRM ("Fetch live lists", "Calls the CRM"), implying an external dependency and freshness, and the platform/kind matrix signals which calls require an integration_id. It does not mention latency or rate limits, keeping it from a 5.

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?

Purpose and downstream destinations are front-loaded, and the dense "Supported:" list is scannable rather than prose. The platform enumeration is long, but every entry carries routing information an agent can use to decide whether the tool will work for a given platform.

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 read-only lookup with no output schema and 100% parameter documentation, the description is largely complete: it covers purpose, downstream consumers, and platform constraints. A brief note on the 200-item cap or the auth/integration precondition would close the remaining gap.

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 baseline is 3. The description earns above baseline by adding a per-kind supported-platform matrix (e.g., stages only Pipedrive, pages/forms only Facebook, inboxes only Follow Up Boss Inbox App), which is not stated in the schema's kind enum. It does not clarify the search/object_type/reference_to interactions, which remain schema-only.

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?

Specific verb (fetch) plus resource (live option lists from a connected CRM), with the exact value kinds enumerated (fields, tags, users, stages, pages/forms, inboxes, ponds). It also states where the results go (ids passed to update_integration or manage_user), which distinguishes it from siblings like get_integrations or manage_user without needing either schema.

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

Usage Guidelines4/5

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

It clearly frames the use case: fetching ids that downstream tools (update_integration field mapping/routing/tag rules, manage_user links) require, and the schema ties integration_id back to get_integrations. There is no explicit when-not or exclusion (e.g., that get_integrations is the prerequisite discovery step), but the context is strong.

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

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