Skip to main content
Glama

Push to CRM

push-to-crm
Destructive

Use when the user wants to push a saved query's results into their connected CRM — e.g., "sync this list to HubSpot."

Supply query_id or run_id. A contacts run may be completed or partial; only validated contacts are delivered.

Requires the client to have already connected the given provider in app settings (Settings > Integrations). Looks up their active integration for that provider and enqueues an async push; the sync itself runs as a background job.

mode="push" (default) creates new CRM records for rows that don't exist yet, and updates existing ones. mode="enrich" only updates CRM records that already exist (matched by domain/email) with DiscoLike data — it never creates new records.

For Salesforce, sf_target_object picks the object companies land on: "leads" (default) or "accounts". Other providers ignore it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "provider": "<provider>"
    },
    "name": "push-to-crm"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'push' creates or updates records; 'enrich' only updates existing onespush
run_idNoOwned contacts run with completed or partial validated results
contextNoWhy you are calling this tool, in a few words. No names or emails.
providerYesCRM provider to push to
query_idNoSaved query ID; supply this or run_id
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
sf_target_objectNoSalesforce only: push companies to 'leads' (default) or 'accounts'

Output Schema

NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, openWorldHint=true, idempotentHint=false), the description discloses that the call only enqueues an async push that runs as a background job, that a contacts run may be partial and only validated contacts are delivered, and that enrich never creates records. These are the operationally important facts an agent needs and none of them are recoverable from the annotations.

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?

The trigger is front-loaded in the first sentence and the remaining paragraphs are organized by concern — inputs, prerequisites/async behavior, mode semantics, provider-specific flag. Some content restates the schema's mode and sf_target_object descriptions, but the duplication is minor and each paragraph carries distinct information.

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 an 8-parameter mutation tool with an output schema, the description covers the prerequisite integration state, the async enqueue/background-job model, data-validation gating on partial runs, and the full mode dichotomy. Nothing an agent needs to call this correctly or set user expectations 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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: it states query_id and run_id are alternatives for the same input, explains enrich matching by domain/email, and clarifies that sf_target_object is ignored by providers other than Salesforce with "leads" as the effective default. It adds limited detail on the plumbing parameters (context, llm_model, conversation_id), but those are self-documented in the schema.

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

Purpose4/5

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

The description opens with a specific verb and resource — pushing a saved query's results into a connected CRM — and names a concrete example ("sync this list to HubSpot"). It doesn't explicitly distinguish itself from similarly named siblings such as crm-import-companies or crm-writeback-domains, so an agent must infer the boundary from the query/run-input framing.

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 gives a clear when-to-use trigger ("Use when the user wants to push a saved query's results...") plus a prerequisite (client must have connected the provider under Settings > Integrations) and routes between the two modes with explicit conditions (push creates or updates; enrich only updates existing records). It stops short of naming alternative tools or stating when not to use this one.

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