Skip to main content
Glama

pptogo

by com.pptogo

find_products

Read-onlyIdempotent

Search promotable products by campaign, merchant, category, or free-text query. Omit all filters to list ALL promotable products. Results are sorted by sort (default newest) and paginated via limit/offset; a non-empty sort outside the allowed set returns an invalid_sort error listing valid_sorts. Only products from billing-active merchants are returned. Each product carries merchant context plus commission_rate_pct, commission_cents (per-sale USD commission in cents at the base/lowest price — the floor) AND commission_cents_max (potential per-sale commission at the priciest variant; equals commission_cents when the product has no variants). Actual commission is on the real purchased variant. Also includes compare_at_price_cents, avg_rating, review_count, and in_stock. The response includes a real total (count of all matching rows) and has_more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order (default newest). `commission` orders by per-product commission (price × merchant rate) DESC.
limitNoMax results per page (default 25, max 100)
queryNoFree-text match against product title (case-insensitive)
offsetNoNumber of results to skip (pagination, default 0)
categoryNoFilter by coarse_category
campaign_idNoFilter to products attached to this campaign (UUID)
merchant_idNoFilter by merchant (UUID — the merchants.id, not shopify_merchants.id)

TDQS

A4.6/5.0
Behavior5/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 agent knows it is a safe read operation. The description goes well beyond annotations by explaining the commission_cents floor vs. commission_cents_max semantics, the invalid_sort error behavior, billing-active filtering, and the real total/has_more pagination indicator.

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?

The description is dense but not bloated, and the core search-and-filter behavior is front-loaded. Each sentence adds meaningful detail, but the commission explanation is long and could arguably be tightened without losing value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex multi-filter tool with 7 optional parameters and no output schema, so the description carries the burden of explaining behavior and returns. It covers filters, default sort, pagination, error behavior, merchant eligibility, commission semantics, and key response fields. The agent gets everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds value beyond the schema: it clarifies commission_cents as the floor at the base/lowest price, commission_cents_max as the potential at the priciest variant, and the invalid_sort error response. It also documents response-level meaning like total and has_more that the schema does not cover.

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?

The description uses a specific verb and resource: 'Search promotable products by campaign, merchant, category, or free-text query.' It clearly distinguishes this from siblings like get_product by positioning it as a search/filter/list operation, not a single-record lookup or campaign-specific action.

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 description gives clear invocation context, including when to omit all filters to return the full product list, pagination defaults, sort behavior, and the billing-active merchant constraint. It does not explicitly name alternatives like get_product, but the usage context is strong enough to guide an agent.

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

All pptogo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools clearly target distinct resources and actions, but there is some overlap: get_profile and get_my_earnings both expose balance/cap information, and list_my_profiles could be confused with get_profile. The descriptions are generally clear enough to avoid serious misselection.

Naming Consistency5/5

Every tool name follows a consistent snake_case verb_noun pattern: get_product, list_campaigns, submit_post, update_profile, etc. The verbs match the intended actions, and there are no mixed naming conventions or vague style deviations.

Tool Count4/5

Twenty tools is slightly heavy, but the count is reasonable for the scope: the server covers products, campaigns, posts, earnings, profiles, notifications, asset uploads, and AI tool usage/reviews. Each tool serves a recognizable purpose, so the size feels like breadth rather than redundancy.

Completeness3/5

Core workflows are present—search products, get campaigns, apply, generate tracking links, submit posts, view earnings, manage notifications—but there are notable gaps. There is no way to list past posts or retrieve a post_id except from submit_post, no list of campaign applications, and no tool discovery endpoint for the AI tool slugs used by declare_tool_usage and write_tool_review.

Resources