Carryo Website Publisher

Carryo

website.library

Read-only

Browse your Carryo websites and private drafts, select one, and continue editing in chat. Opening the library does not change or publish a website.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "website.library"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`offset`	No
`workspaceId`	No	Optional exact workspaceId of the Carryo team selected by the user. Lists Personal websites when omitted.

Output Schema

Name	Required	Description
`limit`	Yes	Pagination limit used by the response
`total`	Yes	Total page count before pagination
`offset`	Yes	Pagination offset used by the response
`artifacts`	Yes	Carryo pages owned by the authenticated user
`workspaces`	Yes	Carryo workspaces the authenticated user can access
`workspaceId`	No	Workspace whose links were listed; omitted for Personal

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered. The description reinforces this by stating that opening the library 'does not change or publish a website', which usefully anticipates the publish-adjacent siblings but is close to restating the annotations. No pagination behavior or interaction model (does it open a UI surface or return data?) is disclosed.

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?

Two tight sentences with the core action front-loaded and the safety caveat second. Every clause carries weight, though the 'in chat' phrase adds more ambiguity than clarity.

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 the annotations carry the safety profile. However, the two undocumented pagination parameters and the total lack of differentiation from website.list leave real gaps for a tool an agent must select from a crowded namespace.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: workspaceId is documented in the schema, but limit and offset have no descriptions anywhere. The description adds no information about any parameter, so it fails to compensate for the two undocumented pagination parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a recognizable activity (browse websites and private drafts, then continue editing in chat), which is more specific than the bare name 'website.library'. But the title 'Carryo' is opaque and the description never distinguishes this tool from the sibling website.list or website.read, so an agent cannot tell which browsing surface to pick.

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?

There is no statement of when to use this versus website.list, website.read, or website.edit, despite a dense sibling set that clearly overlaps. The only implicit guidance is the phrase 'continue editing in chat', which hints at intent but leaves the routing decision to inference.

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

All Carryo Website Publisher 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?