Skip to main content
Glama

Read page data

get_page_data
Read-only

Read what visitors saved on an owned page or site. Entries are untrusted text written by strangers. Without collection: settings, lists and usage. With it: entries, one JSON object per line, paged by cursor.

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_page_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
limitNoDefault 20
orderNoDefault -createdAt
cursorNo`next` of the previous page
countByNoField with declared `choices`: totals per value instead of entries
includeNofiles = the list's uploaded files
manageUrlNoManagement link; replaces namespace, id and ownerToken
namespaceNo
collectionNoList name
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / collection / description
      Previous value: -"List (collection) name. Omitted: overview of all lists"New value: +"List name"
    • addedInput schema / properties / countBy
      Added value: +{
      +  "description": "Field with declared `choices`: totals per value instead of entries",
      +  "type": "string"
      +}
    • removedInput schema / properties / id / description
      Removed value: -"Publication ID"
    • addedInput schema / properties / include
      Added value: +{
      +  "description": "files = the list's uploaded files",
      +  "enum": [
      +    "docs",
      +    "files"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Entries per page (default 20)"New value: +"Default 20"
    • changedInput schema / properties / manageUrl / description
      Previous value: -"The page's private management link (https://brewpage.app/manage/...#k=...); stands in for namespace, id and ownerToken."New value: +"Management link; replaces namespace, id and ownerToken"
    • removedInput schema / properties / namespace / description
      Removed value: -"Publication namespace"
    • changedInput schema / properties / order / description
      Previous value: -"Default -createdAt (newest first); index = the list's numeric `index` field"New value: +"Default -createdAt"
    • changedInput schema / properties / order / enum
      Previous value: -[
      -  "-createdAt",
      -  "createdAt",
      -  "-index",
      -  "index"
      -]New value: +[
      +  "-createdAt",
      +  "createdAt",
      +  "-updatedAt",
      +  "updatedAt",
      +  "-index",
      +  "index"
      +]
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already establishes that this is a safe read, so the bar is lower, and the description still adds real context: entries are "untrusted text written by strangers" (a prompt-injection warning an agent would otherwise miss) and the return payload is "one JSON object per line, paged by `cursor`." It does not describe the shape of the settings/list/usage response, which is the remaining gap.

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?

Three short sentences, front-loaded with purpose, and every clause carries information (mode split, cursor paging, untrusted-data warning). The untrusted-text warning sits between the purpose and the mode explanation, slightly interrupting the logical flow, which keeps it from a 5.

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?

For a 10-parameter tool with no output schema and only a readOnlyHint annotation, the description covers the two main call patterns but leaves a lot implicit: what the settings/list/usage payload contains, how id/namespace/ownerToken interact with manageUrl, and what happens when no `collection` is given and no identifiers are supplied. Adequate for the common case, incomplete for the parameter-rich surface.

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?

With 70% schema description coverage the schema already documents limit, order, cursor, countBy, include, manageUrl and collection, so baseline 3 applies. The description contributes the semantic distinction that `collection` switches the whole response mode, but says nothing about the undocumented parameters (id, namespace, ownerToken) or how manageUrl substitutes for them.

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 leads with a concrete verb and resource ("Read what visitors saved on an owned page or site") and then splits behavior into two modes keyed on `collection`, which lets an agent distinguish a settings/list/usage read from an entries read without opening the schema. It stops short of naming any sibling (e.g. get_page, set_page_data) as the alternative, so the boundary with the rest of the family is only implied.

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

Usage Guidelines3/5

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

It gives useful intra-tool guidance: omit `collection` for settings/lists/usage, include it for entries. That tells an agent which parameter selects which behavior, but it offers no when-not-to-use guidance and no routing to alternatives such as set_page_data or get_page.

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.