Rempa

Add products to track

add_products

Idempotent

Add up to 20 products to a project's product tracking (products add-on), by their page address or their name. This BILLS the account: each active product costs per month $5 (updated every week), $8 (every 3 days) or $12 (every day), 20% less with yearly billing, invoiced now on the subscription, prorated. Confirm the products and the frequency with the person before calling it. Products already tracked are skipped. Rempa then reads each page and drafts its prompts; the first results come within the hour. Refused on the free trial, over the account's product limit, or when the payment fails (then nothing is added). Returns the products added and the new monthly total. An OAuth connection needs the permission to update.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "products": "<products>"
    },
    "name": "add_products"
  }
}

Input Schema

Name	Required	Description
`project`	Yes	The project: its id or its address (for example "acme-france"), as returned by list_projects.
`products`	Yes	The products: a url, a name, or both, for each.
`frequency`	No	How often they are updated: weekly ($5/month each), every3 ($8) or daily ($12). Default weekly.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses critical behavior: the call bills the account, pricing varies by frequency, charges are invoiced now and prorated, already-tracked products are skipped, prompt drafting happens asynchronously, refusals add nothing, and the return includes added products and the new monthly total.

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 front-loaded and dense with high-value information appropriate for a billing-sensitive mutation. It repeats some schema-provided details, especially prices and the 20-product cap, but the extra wording is largely justified by the financial risk.

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?

There is no output schema, yet the description explains the return value. It also covers billing side effects, preconditions, refusals, idempotent skipping behavior, and OAuth permission needs, which is complete for this 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?

Schema coverage is already 100%, so the baseline is 3. The description adds meaningful billing semantics for the frequency parameter, including yearly discounting, immediate invoicing, and proration, though it repeats several schema details such as the 20-product limit and price tiers.

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 opens with a specific verb and resource: adding up to 20 products to a project's product tracking by page address or name. It clearly distinguishes this from read-oriented siblings such as list_products and get_product.

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?

It gives strong usage context: confirm products and frequency with the person before calling, and it lists refusal conditions such as free trial, account limit, and payment failure. It does not explicitly name alternative tools for checking existing tracked products, so it stops short of a full when-to-use/when-to-use-alternative guide.

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

All Rempa 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?