Retrieve pages belonging to a specific Service Portal by providing its sys_id. Filter results by title or ID and limit output to find the exact pages you need.
List pages that belong to a Service Portal
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max records to return (default 50) | |
| query | No | Filter pages by title or id | |
| portal_sys_id | Yes | sys_id of the parent portal |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, which the description aligns with. The description adds minimal behavioral context, such as the implied read-only nature of listing, but doesn't disclose additional traits like pagination or return details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, clear sentence with no redundant wording. It's efficiently front-loaded and doesn't waste tokens.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list operation with fully documented parameters and readOnly/openWorld annotations, the description is sufficient. It doesn't provide an output schema, but that's not required, and the description gives enough context for the tool's purpose.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all three parameters. The description adds no additional parameter semantics beyond what's already in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (List), the resource (pages), and the scope (belonging to a Service Portal). This distinguishes it from sibling tools like list_portals and list_portal_widgets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives such as get_portal_page or list_portals. The description only states what it does without any context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.