Skip to main content
Glama
Sign In

AnalyticsProof

by com.analyticsproof
OverviewDiscussionsAdmin

Remove a standing dataLayer ignore

delete_datalayer_ignore
DestructiveIdempotent

Remove a standing dataLayer ignore (permission: edit)

Delete one of the journey's ignore decisions by id. A decisionId that does not belong to this journey is a 404.

Find the decisionId with list_datalayer_decisions (decision ignored). From the next scan the element is reported again whenever it still differs from the baseline.

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": {
      "id": "<id>",
      "decisionId": "<decisionId>"
    },
    "name": "delete_datalayer_ignore"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJourney id: from GET /journeys or the POST /journeys answer.
decisionIdYesIgnore decision id: from GET /journeys/{id}/datalayer/decisions (decision ignored) or the POST …/ignores answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / decisionId / description
      Added value: +"Ignore decision id: from GET /journeys/{id}/datalayer/decisions (decision ignored) or the POST …/ignores answer."
    • addedInput schema / properties / id / description
      Added value: +"Journey id: from GET /journeys or the POST /journeys answer."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false), the description adds the required permission ('permission: edit'), the error semantics ('A decisionId that does not belong to this journey is a 404'), and the post-condition ('From the next scan the element is reported again whenever it still differs from the baseline'). That is exactly the kind of context annotations cannot express.

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-loads the action and permission requirement, then the id semantics, then the lookup hint and downstream effect. Slight redundancy between the first line and 'Delete one of the journey's ignore decisions by id', but every sentence carries usable 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 a two-parameter destructive mutation with no output schema, the description covers the prerequisite lookup, the error case, the permission gate, and the reversible/observable effect on future scans. Nothing an agent needs to invoke it safely 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 coverage is 100%, so the schema already documents both UUID parameters and their sources, giving a baseline of 3. The description adds scoping meaning the schema lacks: a decisionId not belonging to the given journey resolves to a 404, telling the agent the two ids are coupled rather than independent.

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 ('Remove a standing dataLayer ignore') and immediately clarifies it as 'Delete one of the journey's ignore decisions by id', which distinguishes it from the sibling ignore_datalayer_element (create) and list_datalayer_decisions (list). An agent can tell exactly which operation this performs without opening the schema.

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?

Gives explicit prerequisite workflow: 'Find the decisionId with list_datalayer_decisions (decision ignored)', naming the sibling to use first and the filter to apply. It does not explicitly state when not to use it (e.g., versus ignore_datalayer_element), which keeps it from a 5, but the context is clear enough to route an agent correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AnalyticsProof toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources