Skip to main content
Glama
samarthanalytics-sj

Samarth GTM MCP Server

Official

ga4_delete_adsense_link

Delete an AdSense link in Google Analytics 4 by specifying the resource name and confirming the deletion. Requires explicit opt-in and confirmation to prevent accidental data loss.

Instructions

[GA4 DELETE] Delete an AdSense link. Requires GA4_MCP_ENABLE_DELETES=true and confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull resource name of the AdSense link 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 present. The description warns about required confirm flag and environment variable, implying destructive nature, but lacks details on outcomes, reversibility, or permissions.

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?

Two short sentences: states purpose and critical usage condition. No unnecessary words.

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 delete operation, the description is adequate but lacks return value info and error handling. Given no output schema, more detail could help.

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 schema already documents parameters. The description adds no extra meaning beyond the tool's purpose and requirements.

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 it deletes an AdSense link, with a distinct verb-resource pair and requirement info. No ambiguity.

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

Usage Guidelines3/5

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

The description includes prerequisites (env var and confirm=true) but does not provide guidance on when to use this tool versus alternatives like creating or updating links, nor any exclusion criteria.

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