Skip to main content
Glama

Visibility Genies

Read scheduled runs

get_scheduled_runs
Read-only

Everything in the workspace that spends on its own: scheduled rank checks, audits with Lighthouse, tracked prompts, competitor watches and AI share of voice refreshes, each with its project, how often it runs, its next run, the most a run and a month of runs may cost as its page quotes it, and whether it waits for approval. Schedules are approved and changed on their pages, never by an agent. Only a member with spend access can read it, within their allowed projects. Free: buys nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
schedulesYes
upToPerMonthUsdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so the safety profile is covered; the description adds context the annotations cannot: an entitlement requirement (spend access) plus project-scope restriction, and the hard rule that schedule mutation happens in the UI rather than through an agent. The opaque closer 'Free: buys nothing' hints that free plans return nothing but is too cryptic to count as a full disclosure.

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

Conciseness3/5

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

The critical constraints (read-only, spend access, project scope) are front-loaded rather than buried, which is good. However, the opening sentence is an overlong run-on stacking five resource types with five field types, and the phrase 'the most a run and a month of runs may cost as its page quotes it' is syntactically tangled. The trailing 'Free: buys nothing' is terse to the point of ambiguity.

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?

An output schema exists, so return shape need not be restated; what remains to cover for a zero-parameter read tool is authorization, scope, and the mutation boundary, and all three are addressed. Only the free-tier behavior is left under-explained.

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?

The input schema has zero properties, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies a single unparameterized workspace-wide listing rather than a filtered query.

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 enumerates the exact resource classes returned (scheduled rank checks, Lighthouse audits, tracked prompts, competitor watches, AI share of voice refreshes) and the fields carried per item (project, cadence, next run, cost caps, approval status). That is far more specific than the title's 'Read scheduled runs' and lets an agent recognize this as the workspace-wide schedule inventory. It stops short of naming a sibling such as read_competitor_refresh to distinguish narrow per-feature reads from this aggregate view.

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 establishes clear preconditions ('Only a member with spend access can read it, within their allowed projects') and an explicit exclusion ('Schedules are approved and changed on their pages, never by an agent'), which tells the agent to use this only for inspection and never for mutation. No positive alternative tool is offered for the narrow per-feature reads, so the routing is clear but not complete.

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.

Resources