Skip to main content
Glama
samarthanalytics-sj

Samarth GTM MCP Server

Official

ga4_delete_calculated_metric

Delete a GA4 calculated metric by passing its resource name and confirming. The delete feature must be enabled.

Instructions

[GA4 DELETE] Delete a calculated metric. Requires GA4_MCP_ENABLE_DELETES=true and confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull resource name of the calculated metric to target, e.g. "properties/123/…/456".
confirmYesMust be true to delete.
Behavior3/5

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

No annotations are provided, so description bears full burden. It correctly flags deletion as destructive and states required conditions, but omits details like irreversibility or impact on other resources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with a tag, front-loaded, no wasted words. Every part earns its place.

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 delete with two parameters and no output schema, description is adequate but lacks behavioral nuance (e.g., return value, consequences). Could elaborate on post-deletion effects.

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% with clear descriptions for both parameters. Description adds no extra meaning, merely restating confirm=true. 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 clearly states 'Delete a calculated metric' using a specific verb and resource, distinguishing it from sibling create/update tools for the same resource.

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 description explicitly lists prerequisites (GA4_MCP_ENABLE_DELETES=true and confirm=true), telling when to use the tool. It does not mention when not to use it, but context from siblings clarifies its deletion-only role.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samarthanalytics-sj/samarth-analytics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server