Skip to main content
Glama

Save Exclusion List

save-exclusion-list

Use when the user wants to exclude specific companies or contacts from future searches — e.g., "don't show me these companies again."

Creates a saved exclusion list of company domains or contact identifiers.

Provide domains for company-based lists, persona_ids for contact-based lists, or both. Optionally apply tags at creation so the list can be found later via tag filters.

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": {
      "query_name": "<query_name>"
    },
    "name": "save-exclusion-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags to apply to the exclusion list (max 20 tags, each 2-50 chars; sanitized to lowercase)
contextNoWhy you are calling this tool, in a few words. No names or emails.
domainsNoList of domains to save (for company-based lists)
llm_modelNoYour model id, or "unknown".
query_nameYesName for the exclusion list
persona_idsNoList of persona IDs to save (for contact-based lists)
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

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world write, and the description usefully adds that tags are applied at creation time so the list is discoverable later. However, idempotentHint=false is left unexplained — an agent is not told that repeated calls may create duplicate lists — nor is there any note on limits or failure behavior.

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?

Four short lines, front-loaded with the trigger before the mechanics, with no redundant restatement of the title. The quoted user example earns its place as an intent cue rather than filler.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile. Remaining gaps are small but real: no duplicate-call behavior for a non-idempotent write and no statement on minimum payload requirements.

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 coverage is 100%, so the baseline is 3. The description adds modest meaning by explaining that domains target companies, persona_ids target contacts, and the two can be combined, but it does not state whether at least one of them is required or how conflicts are handled.

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?

"Creates a saved exclusion list of company domains or contact identifiers" is a specific verb plus resource, and the opening clause frames the user intent. It does not name or distinguish itself from plausible siblings such as crm-suppress, so an agent must infer which suppression mechanism applies.

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?

The trigger is explicit and illustrated ("don't show me these companies again"), which is strong when-to-use guidance. There are no when-not-to-use conditions or named alternatives, so an agent facing a similar suppression need has no routing signal.

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