Skip to main content
Glama

Select GA4 Property

select_ga4_property
Idempotent

Remember the user's explicitly chosen GA4 property for this site. First use list_ga4_properties / listGa4Properties and present the property name and hostname evidence. Call only after the user explicitly confirms that choice; never select based solely on a guess. Requires the returned connectionId and property. Set property:null to explicitly clear the selection. Validates ownership and live property access. Does not install tracking or alter Google settings. Fresh SEO and AI referral queries retain the exact site hostname filter.

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": {
      "siteId": "<siteId>",
      "property": "<property>",
      "confirm": "<confirm>"
    },
    "name": "select_ga4_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesOwned Nimo site ID from list_sites
confirmYesTrue only after explicit user confirmation
propertyYesConfirmed properties/NUMBER resource; null clears selection
connectionIdNoGoogle connection ID from list_ga4_properties; required to select

Output Schema

NameRequiredDescriptionDefault
statusYes
selectionNoRequired when selected
reasonCodeNoPresent when unavailable

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
  2. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "properties": {
      +      "status": {
      +        "const": "selected"
      +      }
      +    },
      +    "required": [
      +      "selection"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "status": {
      +        "const": "unavailable"
      +      }
      +    },
      +    "required": [
      +      "reasonCode"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "status": {
      +        "const": "cleared"
      +      }
      +    }
      +  }
      +]
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
  4. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
  6. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  7. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
  8. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  9. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description adds real value beyond them: ownership and live property access are validated, null clears the selection, and nothing in Google's settings or tracking is modified. It does not say what happens when validation fails or what the write returns. The closing sentence about fresh SEO and AI referral queries is behaviorally relevant but too compressed to be actionable.

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?

The purpose and the confirmation gate are front-loaded, and every sentence carries an instruction or a constraint. The telegraphic, fragment-heavy style makes it denser than it needs to be, and the final sentence's relevance is not obvious on first read.

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

Completeness4/5

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

For a persisted-selection write with a full output schema and annotations, the definition covers prerequisites, evidence requirements, clearing, and side effects. The main remaining gap is failure behavior, and the ambiguous trailing sentence about downstream queries.

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 the baseline is 3. The description does add one genuine detail beyond the schema: connectionId is only 'required to select', which clarifies why it sits outside the required list, and it reinforces the property:null clearing 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 first sentence states a specific verb and resource: persist ('remember') the user's explicitly chosen GA4 property for a site. It is immediately distinguishable from list_ga4_properties, which the description names as the discovery step rather than the selection step.

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

Usage Guidelines5/5

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

It gives an explicit ordering rule ('First use list_ga4_properties ... present the property name and hostname evidence'), a hard precondition ('Call only after the user explicitly confirms'), and a prohibition ('never select based solely on a guess'). It also bounds scope with 'Does not install tracking or alter Google settings', so the agent knows what this call is not for.

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.