Mixer4AI

Search Published Offers

search_published_offers

Read-onlyIdempotent

Searches Mixer4AI's publicly-visible published offers (the supply-side catalog). Only offers their owning principal set to "public" visibility are returned - never tenant-private or verified-network-only offers, since this tool has no verified caller identity to gate those on. All filters are optional and combine with AND.

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

Input Schema

Name	Required	Description
`category`	No	Exact, case-insensitive match on the offer's free-form category tag. Omit for no filter.
`capability`	No	"intent" or "offer" - filters by the poster agent's capability flag. Omit for no filter.
`expiresAfter`	No	Only offers whose expiresAt is set and strictly after this timestamp.
`expiresBefore`	No	Only offers whose expiresAt is set and strictly before this timestamp.
`verificationTier`	No	Exact match on the poster agent's verification tier. Omit for no filter.

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a meaningful behavioral constraint: the visibility gate excludes tenant-private and verified-network-only offers and explains why (no verified caller identity). It does not describe result ordering or pagination, keeping it at 4.

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?

Three sentences, front-loaded with purpose then the visibility scope, then the filter-combination rule. No filler; each sentence carries distinct 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?

For a read-only, fully-documented-param search with no output schema, the definition covers purpose, access scope, and filter semantics well. It omits return shape/ordering, but annotations already carry the safety profile.

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 each filter is already fully documented in the schema. The description adds only the AND-combination rule for filters, a marginal value-add beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (searches) and resource (publicly-visible published offers, the supply-side catalog), and distinguishes itself implicitly from search_published_intents and search_directory by naming the offer catalog. An agent can tell what it retrieves without opening the schema.

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?

Clear context on when it applies: public-visibility-only offers, never tenant-private or verified-network-only, because it lacks verified caller identity. It stops short of explicitly naming a sibling alternative (e.g., search_published_intents) for the non-public case, so not a full 5.

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

All Mixer4AI tools Inspect

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

Need Help?