Marcora

create_external_share

Creates a public share link for content, with optional expiration. Accessible by anyone without a Marcora account. Workflow: 1) Get content_id from list_content. 2) Optionally provide expires_at as a Unix timestamp to limit access duration. 3) Returns a ready-to-use share_link URL that is accessible publicly, but won't be indexed by search engines.

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": {
      "content_id": "<content_id>"
    },
    "name": "create_external_share"
  }
}

Input Schema

Name	Required	Description	Default
`content_id`	Yes	The ID of the content you wish to share
`expires_at`	No	Optional expiry for the share link, as a Unix timestamp in MILLISECONDS (e.g. Date.now() + 7 days). It is compared directly against the current time in milliseconds, so a seconds-based timestamp will make the link appear already expired. Omit it — or pass anything that is not a number, which is ignored — to create a link that never expires.

Output Schema

Name	Required	Description	Default
`share_link`	Yes	Public URL (https://app.marcora.ai/s/<token>) anyone can use to view the content

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior. The description adds genuinely useful context beyond them: the link is public to anyone without an account, is excluded from search-engine indexing, and is returned as a ready-to-use URL. It does not warn that repeated calls create separate links, which matters given idempotentHint=false.

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?

Front-loaded purpose followed by a numbered workflow, so an agent can scan it quickly. There is minor redundancy: public accessibility is stated twice ('Accessible by anyone without a Marcora account' and 'accessible publicly'), but nothing is bloated.

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 2-parameter creation tool with an output schema, the description covers purpose, precondition, expiry semantics, and the security profile of the resulting link. The only missing piece is confirmation that each invocation mints a new independent link, which is implied by the annotations rather than stated.

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% and the schema already explains expires_at in milliseconds and the non-number-ignored behavior in more detail than the description. The description only adds a workflow pointer for obtaining content_id, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: 'Creates a public share link for content', plus the defining traits (public access, optional expiration). No sibling tool offers sharing, so there is no ambiguity about which tool to pick for this job.

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?

Gives a concrete precondition for use ('Get content_id from list_content') and the optional-expiry branch, which is clear guidance for when this tool applies. It stops short of saying when NOT to share externally or what alternatives exist (e.g. internal-only access), so it falls short of a 5.

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

All Marcora tools Inspect

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

Need Help?