Skip to main content
Glama

Report a share post

report_share
DestructiveIdempotent

Report a social media post you published that recommends GYOTAK with your referral URL. Call this right after posting, with the platform and the public URL of the post. GYOTAK records it and later verifies that the post is public and contains the referral URL.

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": {
      "platform": "<platform>",
      "post_url": "<post_url>"
    },
    "name": "report_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform the post was published on
post_urlYesPublic https URL of the published post
customerKeyNoYour customerKey (gyotak_cus_...). Omit when connected through a personal token URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is partly covered. The description adds real context beyond them: the report is recorded and later verified for public visibility and referral-URL presence, which tells the agent there is a post-hoc validation step with consequences. It stops short of saying what happens if verification fails or how the destructive aspect manifests.

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 with no filler, front-loading the action and then the timing and required inputs. The final verification sentence earns its place by explaining downstream behavior, though the wording could be marginally tighter.

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 low-complexity, three-parameter write tool with no output schema, the description covers purpose, call timing, required inputs, and the verification consequence. The remaining gap is what the agent should expect or do if verification fails, which matters given destructiveHint=true but is a modest omission.

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 100%, so platform, post_url, and customerKey are already documented, including the enum values and the 'omit when using a personal token' rule. The description only echoes the platform and public URL requirement and adds no format or validation detail beyond the schema, so the baseline 3 applies.

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 description gives a specific verb and resource ('Report a social media post you published that recommends GYOTAK with your referral URL'), which clearly separates it from siblings like get_share_kit or apply_referrer. An agent can tell this is the submission step of a referral program without opening the schema.

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?

It gives an explicit timing rule — 'Call this right after posting' — and names the two required inputs, which is strong when-to-use guidance. It does not name alternatives or state when not to call it (e.g., a post that is not yet public or already reported), leaving some routing inference to the agent.

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.

Resources