Xyla AI

Upcoming posts

upcoming_posts

Read-onlyIdempotent

Lists the posts this Xyla shop will publish, day by day, for up to 7 days from a start date (the shop's today if left out). Each post has its platforms, send time in the shop's time zone, type, caption and media links. Posts waiting for approval are not here: use pending_approvals.

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

Input Schema

Name	Required	Description	Default
`days`	No	How many days to show, 1 to 7. Defaults to 7.
`start_date`	No	First day to show, as YYYY-MM-DD in the shop's time zone. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds useful context on top: the default start date is the shop's today, times are expressed in the shop's time zone, and there is no output schema, yet the returned fields (platforms, send time, type, caption, media links) are enumerated here. That fills the gap the missing output schema would otherwise leave.

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?

Two sentences, zero filler. The core behavior and scope are front-loaded, with the sibling routing clause placed last where it belongs.

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?

For a small read-only listing tool with two optional params and no output schema, the description covers scope limits, default behavior, time-zone handling, returned fields, and the exclusion boundary. Nothing an agent needs in order to call it correctly is missing.

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 schema already documents both parameters, setting the baseline at 3. The description adds a little semantic clarity by framing days as the window length and start_date as the shop's today when omitted, reinforcing the time-zone semantics rather than merely repeating the schema.

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 ("Lists the posts this Xyla shop will publish") plus the scope bounds (day by day, up to 7 days from a start date). It explicitly differentiates itself from the pending_approvals sibling, so an agent can route without opening either schema.

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?

Gives both a positive condition (posts scheduled to publish in a date window) and an explicit exclusion with the alternative named: "Posts waiting for approval are not here: use pending_approvals." That is a clear when-to-use / when-not-to-use / alternative triple.

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

All Xyla AI 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?