Skip to main content
Glama

Write Back CRM Domains

crm-writeback-domains
Destructive

Writes matched domains from a saved match query when the user wants the matched domains written back onto their CRM records — e.g., "update my Salesforce accounts with the matched websites."

Takes the saved match query's ID and updates each CRM record whose match confidence is at least min_confidence. Runs as a background job.

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>",
      "query_id": "<query_id>"
    },
    "name": "crm-writeback-domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoWhy you are calling this tool, in a few words. No names or emails.
providerYesCRM provider whose records should be updated
query_idYesID of a saved company match query
llm_modelNoYour model id, or "unknown".
min_confidenceNoOnly write back matches with at least this confidence (50-100)
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.

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/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risk profile is partly covered. The description adds one genuinely new behavior — it 'runs as a background job' — but says nothing about what is overwritten on the CRM record (existing domain values?), whether partial updates are skipped, or what permissions are needed. For a destructive mutation, that overwrite semantics gap matters.

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?

Intent and example come first, followed by mechanics and the background-job note — well front-loaded and short. There is minor redundancy in the opening clause ('Writes matched domains ... the matched domains written back'), which could be tightened.

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?

An output schema exists, so return values and job-tracking details need not be spelled out here. Given the six documented parameters and the annotation coverage, the description supplies what an agent needs to pick the tool and call it with provider, query_id, and a confidence floor.

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 schema already documents provider, query_id, min_confidence range, and the analytics fields. The description restates that query_id refers to a saved match query and that min_confidence gates which matches are written, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 pairs a specific verb and resource ('Writes matched domains ... onto their CRM records') with a concrete user-intent example ('update my Salesforce accounts with the matched websites'). An agent can distinguish it from crm-writeback-segments or push-to-crm by the source (a saved match query) and the target (matched domains).

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 activation trigger: use when the user says the matched domains should be written back onto CRM records. It also states the precondition (a saved match query ID) and the confidence filter, but it never says when not to use it or points to alternatives such as crm-writeback-segments or push-to-crm for other writeback shapes.

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