Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Link or unlink this project in a Brand, Genfluencer, Series or Film

native.genads_link_location
DestructiveIdempotent

Link or unlink this project in a Brand, Genfluencer, Series or Film. A location grants no advertising authority.

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

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.2/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 safety profile is covered. The description adds one genuinely useful piece of context — that linking a location confers no advertising authority — but says nothing about what unlinking tears down, permission gating, or how link vs unlink differ in side effects.

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?

Two short sentences with the operation front-loaded and no filler. The second sentence earns its place as a scope caveat, though its phrasing is terse enough to be ambiguous about what 'location' refers to without consulting the schema.

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, five required, nested objects, an output schema and a strict invocation protocol (session skill proofs, catalog version), the definition covers the what but not the how. Because an output schema exists the return shape needn't be described, but the required bootstrap parameters and the destructive/unlink consequences are left entirely to the schema and annotations.

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 coverage is 50%, with read_skills, publication_proposal_id and expected_catalog_version self-documented and work_id, arguments and request_key undocumented. The description's list 'Brand, Genfluencer, Series or Film' loosely maps to the parent.kind enum (noting the schema says 'influencer' rather than 'Genfluencer') and implies 'this project' is work_id, but it explains nothing about the operation_id/expected_revision protocol or the difference between link and unlink.

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?

States a specific verb pair (link/unlink) and resource (a project's placement in a Brand, Genfluencer, Series or Film), so the operation is clear. It does not distinguish itself from near-name siblings such as native.link_genads_project, native.genads_link_experiment, native.attach_project or native.detach_project, which an agent would have to open to disambiguate.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The closest thing to guidance is the caveat 'A location grants no advertising authority', which is a semantic note rather than a routing rule, and it does not say which sibling to pick for ad authority, experiments, or project attachment.

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