Skip to main content
Glama

Coline

Publish a page

publish_page
DestructiveIdempotent

Publishes a note to the web at the person's Coline address, for anyone with the link.

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": {
      "workspace": "<workspace>",
      "fileId": "<fileId>"
    },
    "name": "publish_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesFile or folder id from list_drive_files, search or fetch.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, destructiveHint=true, idempotentHint=true and readOnlyHint=false. The description usefully adds that the result is world-readable by anyone holding the link, which gives concrete meaning to the open-world hint. It does not disclose what destruction means here (e.g. overwriting an existing published version or prior settings) or any permission requirements, which matters for a destructive mutation.

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?

A single economical sentence with the audience/visibility consequence front-loaded after the action. No filler, though it is thin enough that a short clarifying clause about the destructive overwrite would not have hurt.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. Still, for a destructive, publicly-facing mutation the description omits what gets overwritten, whether a password is needed, and how to reverse it via unpublish_page.

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% – both workspace and fileId are documented with source hints (workspaces.list, list_drive_files). The description adds nothing about either parameter, so the baseline of 3 applies.

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 (publishes) and resource (a note/page), plus the resulting state: reachable at the person's Coline address by anyone with the link. An agent knows exactly what the call accomplishes. It does not contrast itself with siblings such as get_published_page or unpublish_page, so it stops short of a 5.

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?

No when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to related operations (unpublishing, adding a password via set_page_password). The public-exposure implication is stated as an outcome rather than as a selection criterion, so the agent must infer when this is the right call.

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