AdCopilot

GA4: create property

ga4_create_property

Create a GA4 property under an Analytics account (accounts/).

Use the Google Ads account's time zone and currency — get_org_context
carries them as the Analytics card's property_defaults; if it has none,
ask the user. time_zone is an IANA name (e.g. "Asia/Kolkata"),
currency_code ISO 4217 (e.g. "INR"). Next: ga4_create_data_stream on the
returned property for the website, which gives the measurement ID.

Tools revision: d80f65c0.

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": {
      "account": "<account>",
      "display_name": "<display_name>",
      "time_zone": "<time_zone>",
      "currency_code": "<currency_code>"
    },
    "name": "ga4_create_property"
  }
}

Input Schema

Name	Required	Description	Default
`account`	Yes
`time_zone`	Yes
`display_name`	Yes
`currency_code`	Yes
`industry_category`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare a non-idempotent, non-destructive create in a closed world, so the description doesn't need to restate that. It adds real operational context: where the mandatory defaults come from, the account ID format, and what the created property is used for next. It doesn't mention duplicate-name behavior or what happens if the account ID is malformed.

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 opening sentence is the action and scope, followed by the prerequisite sourcing then the next step — a sensible front-loaded order with no filler. The trailing "Tools revision: d80f65c0." line is noise that does not help an agent invoke the tool.

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?

With an output schema present, return values need no explanation, and the description instead covers prerequisites, parameter formats, and sequencing. It's nearly complete for a 5-parameter create; only industry_category's meaning and any duplicate-checking behavior are absent.

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 description coverage is 0%, so the description must carry the load, and it does for the three ambiguous parameters: account format (accounts/<id>), time_zone as an IANA name with an example, and currency_code as ISO 4217 with an example. display_name is self-evident, but industry_category is never mentioned in the description or the schema, leaving one optional parameter opaque.

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 with its parent scope: "Create a GA4 property under an Analytics account (accounts/<id>)". It also names the follow-on sibling ga4_create_data_stream, making the boundary between this tool and the next step in the GA4 flow unambiguous.

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 sourcing guidance: pull time_zone and currency_code from get_org_context's Analytics card property_defaults, and ask the user if absent. It also prescribes the next tool to call. What's missing is any when-not-to-use guidance, e.g. how to check whether a property already exists via ga4_list_properties before creating.

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

All AdCopilot tools Inspect

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

Need Help?