Skip to main content
Glama
samarthanalytics-sj

Samarth GTM MCP Server

Official

ga4_google_ads_links_list

List Google Ads links for a GA4 property, retrieving linked customer IDs and flags for personalized advertising and auto-tagging. Read-only operation.

Instructions

List Google Ads links for a GA4 property (linked customer ID, personalized-advertising and auto-tagging flags). Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
pageTokenNoContinuation token to resume listing from a previous truncated result.
maxPagesNoMaximum number of API pages to fetch (default 50). If more pages remain, the result includes truncated:true and a nextPageToken.
Behavior3/5

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

With no annotations provided, the description must convey behavioral traits. It correctly states 'Read-only', implying no destructive effects. However, it omits details on pagination behavior (though maxPages hint is in schema) and potential errors. It adds marginal value beyond the schema by clarifying the scope of data returned.

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?

The description is a single sentence that immediately states the action and resource, then provides clarifying details in parentheses. Every word contributes meaning without redundancy. It is front-loaded and efficient.

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?

The tool has 3 parameters, no output schema, and no annotations. The description covers the basic purpose and read-only nature but fails to explain the return format, pagination handling, or error conditions. Given the missing output schema, more detail on what the list returns would enhance completeness.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema provides. It mentions the data fields returned, but that is output context, not parameter semantics.

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 uses the specific verb 'List' and resource 'Google Ads links for a GA4 property', and further specifies the included fields (linked customer ID, personalized-advertising and auto-tagging flags). This clearly distinguishes it from sibling tools, none of which target Google Ads links.

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 states 'List Google Ads links' and 'Read-only', providing context for safe use. While no explicit when-not-to-use or alternatives are given, the tool's unique purpose among siblings makes such guidance less critical. The read-only tag is a helpful guideline.

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