Skip to main content
Glama

Audit CRM Companies

crm-audit-companies
Destructive

Use when the user wants to clean up their CRM — find which companies in it have gone out of business — e.g., "which of my HubSpot accounts are dead?"

Checks every CRM company's website against DiscoLike's index (works even for domains DiscoLike no longer actively indexes) and writes an operating status onto each record: "active", "closed", "redirected to ", or "unknown". On HubSpot/Pipedrive the status lands in a DiscoLike Domain Status property (filter on it to bulk-archive dead accounts natively); on Salesforce it's a "DiscoLike status:" line in Description. Closed companies are also saved as a reviewable domain list.

Runs as a background job over up to 10,000 companies.

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": "crm-audit-companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoWhy you are calling this tool, in a few words. No names or emails.
providerYesCRM provider whose companies should be audited
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.

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
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the description's job is to add specifics — and it does: it discloses exactly which field gets written per provider, that closed companies are also persisted as a reviewable domain list, and a hard scale ceiling of 10,000 companies per background run. It does not address re-run/overwrite semantics (idempotentHint=false) or what happens to prior or manually edited status values, which is the remaining gap for a destructive tool.

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?

Front-loaded with the 'Use when' trigger, then behavior, then per-provider write targets, then scale limit — a sensible priority order with no filler sentences. Slightly dense paragraphing and a stray unmatched opening quote before the example utterance are minor blemishes.

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?

An output schema exists, so return values need not be explained, and the description covers the things an agent still needs: the trigger, the write behavior, provider-specific destinations, and the 10,000-company batch limit. What is missing is runtime context — expected duration, whether a missing or unconnected CRM integration causes an error, and how a re-run interacts with already-written statuses.

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 earns above that by explaining the consequence of the `provider` enum value — the status lands in a DiscoLike Domain Status property on HubSpot/Pipedrive but in a 'DiscoLike status:' line in Description on Salesforce. The telemetry parameters (context, llm_model, conversation_id) are left to their schema descriptions, which is acceptable.

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?

States a specific verb and resource ('audit' / 'every CRM company's website') plus the exact outcome written to each record, so it is distinguishable from siblings like crm-match-companies or crm-writeback-domains. The provider-specific write locations (DiscoLike Domain Status property vs. Salesforce Description line) further sharpen what this tool uniquely does.

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?

Opens with an explicit trigger ('Use when the user wants to clean up their CRM — find which companies have gone out of business') and gives a concrete example utterance. It never names a when-not condition or a sibling alternative for overlapping cases (e.g., when to use crm-match-companies or crm-suppress instead), so it stops short of a 5.

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