Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Read saved available pixels for conversion delivery under the separate conversions permission

native.genads_conversion_destinations
DestructiveIdempotent

Read saved available pixels for conversion delivery under the separate conversions permission. No campaign reports or diagnostics are included. Refresh through genads_ad_action action conversion_destinations.

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_conversion_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYes
argumentsYes
read_skillsYesExact 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_keyYes
publication_proposal_idNoFor native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
expected_catalog_versionYesFor 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior1/5

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

The description frames this as a read of saved state ("Read saved available pixels"), while annotations declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true. Nothing in the text explains why a read of saved pixels would be destructive or non-read-only, so an agent has no way to reconcile the two. This is a direct mismatch rather than a benign omission.

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 short sentences, front-loaded with the purpose and followed by the exclusion and the refresh path. No filler, though the phrasing ("pixels for conversion delivery") is jargon-dense and slightly compressed for a reader unfamiliar with the domain.

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?

An output schema exists, so return values need not be described. However, for a tool whose description invokes a "separate conversions permission" and whose annotations flag destructive behavior, the text says nothing about how that permission is obtained or what side effects occur, leaving meaningful gaps against its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Six parameters with only 50% schema description coverage, and the description supplies no parameter information whatsoever. The nested arguments object (account_id required, optional operation_id) and the work_id / request_key / read_skills requirements are left entirely to the schema, with the ambiguous operation_id undocumented in both places.

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?

Names a specific verb and resource: reading saved available pixels for conversion delivery, scoped to the separate conversions permission. It also carves out what it is not (no campaign reports or diagnostics), which separates it from genads_campaigns / genads_read_report. It stops short of distinguishing itself from closely related siblings such as genads_conversion_review or genads_ad_accounts.

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?

States a clear exclusion ("No campaign reports or diagnostics are included") and gives an explicit route for the refresh case: genads_ad_action with action conversion_destinations. What is missing is a positive trigger — when an agent should pick this over genads_conversion_batches, genads_conversion_result, or genads_conversion_review.

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

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