Skip to main content
Glama

sb_bind

Binds page nodes to real store data so products replace placeholder text, and attaches add-to-cart or buy-now actions to buttons.

Instructions

Bind a node to real store data so the page shows actual products, not placeholder text. action makes a button a purchase control.

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": {
      "id": "<id>",
      "source": "<source>",
      "field": "<field>"
    },
    "name": "sb_bind"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
fieldYesWhere the value lands, always "specials.<key>"
forceNoOverride a render-inference guard; reported as forced
actionNoPass product.id + specials.boundProductId
sourceYese.g. article.author, article.categories, article.content, article.date; 96 in all, plus record.fld_<16 hex> / record.id for a Collections row; a wrong one is refused with the list
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.103.0
    • changedInput schema / properties / source / description
      Previous value: -"e.g. article.author, article.categories, article.content, article.date; 95 in all, plus record.fld_<16 hex> / record.id for a Collections row; a wrong one is refused with the list"New value: +"e.g. article.author, article.categories, article.content, article.date; 96 in all, plus record.fld_<16 hex> / record.id for a Collections row; a wrong one is refused with the list"
  2. Changed1 schema field changedv0.98.3
    • changedInput schema / properties / source / description
      Previous value: -"e.g. article.author, article.categories, article.content, article.date; 94 in all, plus record.fld_<16 hex> for a Collections field; a wrong one is refused with the list"New value: +"e.g. article.author, article.categories, article.content, article.date; 95 in all, plus record.fld_<16 hex> / record.id for a Collections row; a wrong one is refused with the list"
  3. Changed1 schema field changedv0.89.0
    • changedInput schema / properties / source / description
      Previous value: -"e.g. article.author, article.categories, article.content, article.date; 79 in all, and a wrong one is refused with the list"New value: +"e.g. article.author, article.categories, article.content, article.date; 94 in all, plus record.fld_<16 hex> for a Collections field; a wrong one is refused with the list"
  4. Changed1 schema field changedv0.63.0
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "Override a render-inference guard; reported as forced",
      +  "type": "boolean"
      +}
  5. Changed1 schema field changedv0.60.1
    • changedInput schema / properties / source / description
      Previous value: -"e.g. article.author, article.categories, article.content, article.date; 78 in all, and a wrong one is refused with the list"New value: +"e.g. article.author, article.categories, article.content, article.date; 79 in all, and a wrong one is refused with the list"
  6. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / action
      Added value: +{
      +  "description": "Pass product.id + specials.boundProductId",
      +  "enum": [
      +    "add_to_cart",
      +    "buy_now"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / source / description
      Previous value: -"One of: article.author, article.categories, article.content, article.date, article.image, article.summary, article.tags, article.title, article.url, category.description, category.image, category.title, category.url, product.compareAtCents, product.compareAtPrice, product.description, product.id, product.image, product.images, product.price, product.priceCents, product.ratingAverage, product.ratingCount, product.title, product.url, product.vendor"New value: +"e.g. article.author, article.categories, article.content, article.date; 78 in all, and a wrong one is refused with the list"
  7. First observedv0.1.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-read-only, non-destructive mutation. The description confirms the page rendering change and button behavior change, but it does not explain reversibility, permissions, or the force and dry_run behaviors.

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?

The description is two compact sentences with the core purpose front-loaded and no wasted text. The second sentence adds useful action-specific context without bloating the definition.

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

Completeness3/5

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

This is a six-parameter mutation tool with no output schema and only limited annotations, so the description should carry more behavioral context. It covers the core binding and action semantics, but omits dry_run and force behavior and does not route the agent away from sibling tools.

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 67%: source, field, force, and action have schema descriptions, while id and dry_run do not. The description adds meaning for action by saying it makes a button a purchase control, but it does not compensate for the undocumented id and dry_run 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 states a specific verb and resource: bind a node to real store data so placeholders are replaced with actual products. It also clarifies that action turns a button into a purchase control. It is clear, but it does not distinguish this tool from nearby siblings like sb_set or sb_connect.

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?

The description implies the use case: replacing placeholder content with real store data and configuring purchase buttons. However, it gives no explicit when-not-to-use guidance or alternatives, and it does not mention prerequisites or how this differs from sb_set or sb_connect.

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