Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Campaigns

tl_campaigns
Read-onlyIdempotent

List current campaigns or show a campaign's sections and products by code. Pass the returned page_url to tl_category_products for all products.

Instructions

List current campaigns, or show one campaign's sections and products.

Without code: campaign landings (code) and promotion pages (page_url). With code: its carousels with a few products each. Pass a page_url to tl_category_products for all products.

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

Input Schema

NameRequiredDescriptionDefault
codeNoLanding code from this tool's list, e.g. 'payday-technolife'. Omit to list campaigns.
products_per_sectionNoProducts to show per carousel of a campaign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • removedInput schema / properties / code / anyOf
      Removed value: -[
      -  {
      -    "pattern": "^[A-Za-z0-9_-]{2,60}$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / code / description
      Previous value: -"Campaign landing code from this tool's list, e.g. 'payday-technolife'. Omit to list current campaigns."New value: +"Landing code from this tool's list, e.g. 'payday-technolife'. Omit to list campaigns."
    • addedInput schema / properties / code / pattern
      Added value: +"^[A-Za-z0-9_-]{2,60}$"
    • addedInput schema / properties / code / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed4 schema fields changedv0.3.0
    • removedInput schema / properties / code / title
      Removed value: -"Code"
    • removedInput schema / properties / products_per_section / title
      Removed value: -"Products Per Section"
    • removedInput schema / title
      Removed value: -"tl_campaignsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_campaignsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the real behavioral trait an agent needs: with a code, only 'a few products each' carousel are returned, and the escape hatch is tl_category_products. It does not say how many campaigns are listed or whether results are paginated.

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?

Two tight sentences, front-loaded with the two operating modes, then the return shape, then the cross-tool routing. No filler.

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 does the work of explaining both return shapes (landing codes and page_urls versus carousels with sample products). It stops short of covering list size, ordering, or pagination, which would matter for the list mode.

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 both parameters are already documented. The description still adds meaning by tying code=null to list mode and to the carousel truncation behavior, which goes slightly beyond the schema text.

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 states a specific verb and resource plus a dual mode: 'List current campaigns, or show one campaign's sections and products.' It also names the fields returned in each mode (code landings, page_url promotion pages), so an agent can distinguish it from sibling category and search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It spells out the conditional usage explicitly: omit code to list campaigns, pass code to drill into one campaign's carousels. It also routes the agent to tl_category_products with a page_url when the full product list is needed, which is a concrete alternative and the condition that selects it.

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