Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Uploaded images

get_uploaded_page_assets
Read-onlyIdempotent

List the images hosted for this account. With a pageId, the ones that page uses — an asset is attached automatically when you publish a page whose markup points at its URL. WITHOUT a pageId, the ones not on any page yet: images generated or uploaded but never published, which is where a wrong crop or an abandoned draft ends up. The two listings do not overlap. Use it before generating a new image — the user may already have one that fits — and to find the id remove_asset needs.

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": "get_uploaded_page_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNoThe page whose images to list. Omit to list the account's unattached images instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent read, so the description doesn't need to repeat that. It adds genuine non-obvious behavior: attachment is automatic when a published page's markup references an asset URL, and the two listings never overlap. Return shape/pagination isn't described, which keeps it short of 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.

Conciseness4/5

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

Front-loaded with the general case, then the two branches, then the usage advice. Every clause carries information; the 'wrong crop or abandoned draft' phrasing is colorful but reinforces which bucket holds in-progress work, so it earns its place.

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 read-only listing tool with no output schema, this covers what an agent needs to choose the mode and act on the result. Only omission is any hint about what fields the assets carry (id, url), though 'find the id' implies ids are returned.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining the semantic consequence of each branch: with pageId you get assets that page uses; without it you get never-published images. That is meaning the schema's terse 'omit to list...' only partially conveys.

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 ('List the images hosted for this account') and then cleanly splits behavior into the two modes selected by pageId. The distinction from sibling asset tools (get_skill_assets, upload_asset, remove_asset) is clear from the described scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to call it before generating a new image so an existing asset can be reused, and to find the id that remove_asset requires. Both the when and the downstream consumer are named, so the agent knows the trigger and the payoff.

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

All Pageree 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