Skip to main content
Glama
Sign In

Hoplix Print on Demand

by com.hoplix
OverviewDiscussionsAdmin

List my campaigns

list_campaigns
Read-onlyIdempotent

Lists the seller's campaigns (a campaign is a design applied to one or more products), newest first, with id, name, URL, status, dates, and products with selling price and colours.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 20)
offsetNoNumber of results to skip, for paging (default 0)
searchNoText to look for in campaign name, id or URL
statusNoOnly campaigns with this status (as returned in the status field)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds critical behavioral information not in the structured fields, specifically that the results are returned 'newest first.' This is a functional trait that affects agent expectations about the data ordering and is highly valuable.

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?

It is a single, dense, and efficient sentence. It front-loads the core functionality, making it highly readable despite its length.

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?

The description successfully defines the object being listed and mentions the key data fields within that object. Given the strong annotations covering safety, the functional description is very complete for this listing tool.

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?

While schema coverage is 100%, the description adds significant semantic value by listing all the specific fields returned (id, URL, status, products with price/colors). This helps the agent understand the structure of the returned data payload beyond just the input parameters.

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 clearly defines the resource ('seller's campaigns') and the action ('Lists'). It also provides a helpful definition of what a campaign is, distinguishing the resource from other database entries. However, it does not explicitly state how this differs from a targeted `get_campaign` call.

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?

Usage is implied: this is used when a broad overview or search is needed. However, it lacks explicit guidance on when to choose this over a sibling tool like `get_campaign` (which focuses on single resource retrieval) or `list_products`.

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

All Hoplix Print on Demand 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