Skip to main content
Glama
Sign In

Campaign Pack

by ai.campaignpack
OverviewDiscussionsAdmin

Get a download link

get_download_url

A link the person can open to get one file — the campaign PDF, a product still, a video. Works for any file in the workspace, including ones too big or too binary to read as text. The link expires within the hour.

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": {
      "path": "<path>"
    },
    "name": "get_download_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile path relative to the workspace, as shown by list_workspace_files.
session_idNoLink a file from a campaign shared with this account rather than its own files. Omit for your own workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive operation, and the description adds genuinely new behavioral context: the generated link expires within the hour, which is critical for an agent deciding when to surface the URL. It does not cover permission or error behavior, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the outcome, then scope, then the expiry caveat. No filler or repeated information.

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 two-parameter retrieval tool with no output schema, the description covers what is produced (an openable link), scope of applicability, and the expiry constraint. Minor gaps around failure modes and link sharing semantics remain but nothing essential is missing.

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 100%, so both 'path' and 'session_id' are already documented in the schema. The description adds only the loose scope statement that the tool works for any workspace file, which matches but does not extend the schema.

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?

The description states a concrete verb and resource ('a link the person can open to get one file') and enumerates examples (PDF, still, video). It implicitly distinguishes itself from read_workspace_file by noting it works for files 'too big or too binary to read as text', though it never names that sibling explicitly.

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?

Clear use context: any file in the workspace, especially large or binary files that cannot be read as text, so an agent can infer this is the retrieval path rather than the read path. It stops short of explicit when-not-to-use or naming the alternative tool.

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

All Campaign Pack 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