Skip to main content
Glama

List the medias you sell on

growwer_list_seller_medias
Read-onlyIdempotent

Lists the media outlets a seller publishes articles on, including each one's state, fees, and performance metrics so you can compare and manage them.

Instructions

Use this when the user asks about the medias they sell articles on: lists them in every state with their fees and performance.

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

Input Schema

NameRequiredDescriptionDefault
sortNoBy creation date, number of published orders or publication rate; a leading `-` sorts descending. Medias with no publication rate come first ascending, last descending. Ties come in id order.-createdAt
limitNoMedias per page, 1 to 100.
stateNoOnly the medias in one of these states, comma-separated: `analyzing`, `pending_review`, `active`, `deactivated`. An unknown state is refused with 422.
offsetNoMedias to skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 the safety profile is covered. The description adds useful return-scope context beyond annotations by saying results include 'every state' and carry 'their fees and performance'.

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?

The description is a single front-loaded sentence that immediately states when to use the tool and what it returns. There is no redundant or wasted text.

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, the description usefully notes that results include fees and performance, and that all states are listed by default. Pagination, sorting, and filtering are fully covered by the schema, though the description itself does not mention those mechanics.

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?

All four parameters are fully documented in the schema, including enum values, defaults, limits, and sorting semantics. The description adds no parameter-specific detail, so the schema does the heavy lifting and 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 verb and resource: it 'lists' the 'medias they sell articles on' in 'every state with their fees and performance'. This clearly identifies the tool's purpose and differentiates it in practice from single-media tools like get_seller_media, though it does not explicitly name that sibling.

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?

The opening clause 'Use this when the user asks about the medias they sell articles on' gives a clear triggering context. It does not explicitly mention when not to use it or name alternatives, so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools