GenFlick

Import a bounded GA4 report for exact dates and grouping

native.genads_import_analytics

DestructiveIdempotent

Import a bounded GA4 report for exact dates and grouping. Reuse operationId after uncertainty. GA4 session attribution is separate from advertising attribution and verified business revenue; preserve all warnings, missing metrics and partial coverage.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.genads_import_analytics"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
`request_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the description's job is to add context. It does add value by warning that GA4 session attribution differs from advertising attribution and business revenue, and that warnings, missing metrics, and partial coverage must be preserved. But it never explains what the destructiveHint actually means for an "import" operation, which is the most consequential undisclosed behavior.

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?

Three tight sentences, front-loaded with the scope statement before the retry rule and the attribution caveat. Nothing is redundant, though the attribution sentence is dense and could be split for scan-ability.

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?

With six parameters, nested objects, and an output schema, the description need not explain return values. It covers the bounded-date contract, idempotency, and data-quality caveats, but leaves the destructive semantics and the limits of maximumRows undocumented, which is a meaningful gap for an import tool.

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 50%, and the description only adds real meaning for operationId via the reuse-after-uncertainty rule. The date/grouping phrasing largely restates from, to, and groupBy that the schema already defines, and maximumRows, connectionId, read_skills, and request_key get no elaboration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Import a bounded GA4 report for exact dates and grouping" names a concrete verb, data source (GA4), and scope (bounded, exact dates, grouping). This differentiates it from analytics siblings such as genads_read_report or genads_analytics_request, though those alternatives are never named, so an agent must infer the routing.

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?

"Reuse operationId after uncertainty" gives one concrete retry guideline that aligns with idempotentHint. However, there is no explicit when-to-use versus genads_analytics_request, genads_read_report, or genads_refresh_analytics, and no stated prerequisites for the required connectionId or catalog version, so routing remains implied.

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

All GenFlick 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?