Skip to main content
Glama

The Marketing Vault

Remove standing rules

delete_standing_rule
DestructiveIdempotent

Removes one or more saved standing rules from a business. Does not use a generation.

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": {
      "rules": "<rules>"
    },
    "name": "delete_standing_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesYesRules to remove, by exact text or id.
business_profile_idNoBusiness id from list_businesses. Defaults to the default Business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false, so the safety profile is covered. The description adds one genuinely new fact — 'Does not use a generation' — which signals quota/cost behavior not present in the structured fields, but that phrase is unexplained and it omits whether deletion is permanent or what happens on partial matches.

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?

Two short sentences with the core action front-loaded and no padding. The trailing 'Does not use a generation' is terse to the point of ambiguity, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter destructive tool with full schema coverage and rich annotations, the description covers the essentials. It still leaves open failure behavior (non-matching text, partial deletions) and the meaning of the 'generation' remark, which matter for a destructive operation.

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 both parameters are already documented, including the text-or-id matching rule and the business default. The description only echoes the bulk nature ('one or more'), adding no meaning beyond the schema; baseline 3 applies.

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 ('Removes one or more saved standing rules from a business'), which cleanly separates it from the add/update/list standing-rule siblings. It stops short of naming any sibling explicitly, but the operation is unmistakable.

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

Usage Guidelines2/5

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

There is no guidance on when to delete versus when to use update_standing_rule, no prerequisites, and no note on what to do when a rule text does not match. Usage must be inferred entirely from the name.

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