Fetch Hive

Copy a shared page into the workspace

use_share

Make the account's own workflow or agent from a Fetch Hive share page the person sends you (a link such as https://app.fetchhive.com/shared/... or its last part). Works for shared workflows and shared agents, the same as the page's "Edit this workflow" button. Free; nothing is run, deployed or scheduled and the original is never changed. Returns the new workflow or agent with its inputs: then run_workflow or run_agent (each quotes the cost first). If a step needs an app that is not connected, use connect_app.

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": {
      "link": "<link>"
    },
    "name": "use_share"
  }
}

Input Schema

Name	Required	Description	Default
`link`	Yes	The share page link the person gave you, or just its slug.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that the operation is free, runs/deploys/schedules nothing, and never changes the original share. It also explains that the result is a new workflow or agent with its inputs. It does not discuss duplicate-copy behavior or permissions, but the key side-effect profile is well covered.

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 definition is front-loaded with the core action and keeps useful context such as cost, non-destructive behavior, and next steps. It is slightly dense with parenthetical examples, but every sentence contributes relevant operational guidance.

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 one-parameter copy tool with no output schema, the description explains what is created, what is not run, and which tools to use next. It is nearly complete, with only minor gaps around permissions or duplicate handling.

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 the single link parameter is already documented. The description repeats that the link can be a full share URL or its last part, adding little beyond the schema's own wording, which matches the baseline for high coverage.

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 states a specific verb and resource: copying a shared workflow or agent from a Fetch Hive share page into the account's own workspace. It also clarifies that this applies to both shared workflows and shared agents, making the tool distinguishable from siblings that run or inspect shares.

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 a clear trigger: use this when the person sends a share page link and wants their own copy. It also names the natural follow-ups (run_workflow, run_agent) and connect_app for missing app connections, though it does not explicitly contrast with alternatives such as get_share, run_share, or use_template.

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

All Fetch Hive tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?