Skip to main content
Glama
Sign In

Pixelesq

by com.pixelesq
OverviewDiscussionsAdmin

Get partial content

get_partial_content
Read-only

Get the content of a partial (header, footer, or other reusable section). A partial is live when publishedRevisionId is set (status PUBLISHED, live true); hasUnpublishedChanges is true when its draft holds edits that are not live yet. By default sections come as a compact outline: ids, types and content (ctx) without layout settings (cfg), empty values left out, and each icon's svgStr markup replaced by a short reference such as svg:1a2b3c4d that a save keeps when it is sent back unchanged. Pass mode "full" for every field. latestRevision.version is the lastVersion save_partial_content needs, latestRevision.headAnchor the anchor publish_partial binds to.

Input Schema

NameRequiredDescriptionDefault
modeNooutline (default): content without layout settings; full: every field, including cfg and icon markupoutline
partialIdYesThe partial ID
projectIdYesThe project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "outline",
+  "description": "outline (default): content without layout settings; full: every field, including cfg and icon markup",
+  "enum": [
+    "outline",
+    "full"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses meaningful behavior: live status via publishedRevisionId, unpublished-change detection via hasUnpublishedChanges, omission of empty values, replacement of icon SVG markup with reusable short references, and the specific latestRevision fields needed by downstream save/publish tools. Nothing contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The purpose is front-loaded in the first sentence, followed by tightly packed but relevant details about status, output compaction, mode selection, and downstream revision fields. There is no filler, and each sentence contributes useful invocation or interpretation context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description explains the returned structure in enough detail for an agent to interpret outline versus full responses, including omitted fields, icon references, and revision metadata. For a read-only get tool with complete parameter coverage, it is sufficiently complete.

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 adds real meaning beyond the schema by explaining the practical effect of mode: outline omits cfg and empty values and compresses icon markup, while full includes every field. ID parameters remain schema-only, which is appropriate given the existing UUID descriptions.

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?

The description opens with a specific verb and resource: 'Get the content of a partial (header, footer, or other reusable section).' It also defines what a partial is, which distinguishes it from sibling tools like get_page_content and get_section_content without requiring the schema to be opened.

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?

It clearly explains the default outline mode versus passing mode "full" for every field, and ties the returned latestRevision fields to save_partial_content and publish_partial. However, it does not explicitly name alternatives such as get_section_content or state when not to use this tool, so it stops short of full routing guidance.

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

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