Skip to main content
Glama

What is posting this week

promo_this_week
Read-onlyIdempotent

What goes out in the next days across every campaign, what in that time is not scheduled yet (and so will not go out unless it is), and what did not go out lately and needs the artist. last_week: the week that ended, as the Last week sheet on Promo shows it: each post that went out with its numbers and where it stands against the artist's own usual on its platform, the one that did best, their music beside the week before, and what works best so far from their own results. A post with an Instagram collaborator invite carries collab (where the invite stands), and invites_to_artist lists the posts on Audora's Instagram that invite the artist and wait for their answer.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead, 1–14. Default 7.
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds useful behavioral detail beyond that: it explains the report covers upcoming posts, unscheduled items, missed posts needing the artist, last week's performance metrics, collab invite status, and invites to the artist.

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 description is informative but dense and not front-loaded; it packs multiple distinct return-value categories into long, run-on sentences. It could be restructured for readability and brevity without losing essential information.

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 no output schema and two parameters, the description does a thorough job explaining the report's contents, including last week's sheet details, collab invites, and invites_to_artist. It covers the key return elements, though the exact shape of the 'this week' section is only implied.

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 description coverage is 100%, so both parameters (days and artist) are fully documented in the schema. The description does not add any syntax, constraints, or meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states a specific report: 'What goes out in the next days across every campaign, what in that time is not scheduled yet... and what did not go out lately and needs the artist,' and then details the last week's results. This is clear enough to identify the tool's purpose, but it does not name or contrast with sibling tools like promo_results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description describes what the tool returns but gives no explicit guidance on when to use it versus alternatives, such as promo_results or get_promo_settings. It lacks any when-to-use or when-not-to-use direction.

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