Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Read the posts scheduled elsewhere

scheduled_posts_read
Read-only

The business's posts scheduled outside Marsell that Marsell knows about (in another tool, a sheet, or on the platform itself), soonest first: each with its id, ref, channel, time, kind, what it is about, its words when known, who told Marsell, and its state: scheduled, published (with its link, once it went out) or cancelled. Reads only.

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

Input Schema

NameRequiredDescriptionDefault
toNoThe window's last day, YYYY-MM-DD (or a time).
fromNoThe window's first day, YYYY-MM-DD (or a time, 2026-10-20T00:00:00Z).
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, destructive, and openWorld behavior. The description adds useful context beyond that: sort order, returned fields, and the three possible states including published link. It omits auth or rate-limit behavior, keeping it from 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-loads the scoped resource and packs return and state information into one sentence. The long field list is justified because there is no output schema, though it is dense and slightly list-heavy.

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?

With annotations covering safety and the schema covering inputs, the main remaining need is return shape, which the description addresses. It still does not clarify date-window defaults or result limits, so it is not fully complete.

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?

Schema coverage is 100%, so from, to, and project are fully documented in the input schema. The description adds no parameter-level meaning such as default window or project-scoping behavior, so the baseline applies.

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?

States a specific resource and scope: business posts scheduled outside Marsell, from another tool, sheet, or platform, returned soonest first. It has a clear read-only verb, though it does not explicitly name a sibling tool for contrast.

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?

The scope implies when to use it, namely retrieving external scheduled posts, but there is no explicit when/when-not guidance or named alternative among the many read siblings. 'Reads only' is not usage guidance.

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

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