Skip to main content
Glama

Extract External Product

extract_external_product

Extract metadata for an external product URL. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "url": "<url>"
    },
    "name": "extract_external_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic URL of the external product page to extract.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / url / description
      Added value: +"Public URL of the external product page to extract."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds substantial context beyond the annotations: a plan-tier restriction, a mandatory precondition check, and a grace-period/resubscribe warning flow that must be surfaced before proceeding. It does not clarify what happens server-side on a successful extraction (for example whether a cached product record is created), which is why readOnlyHint=false looks slightly surprising for an 'extract' operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is correctly front-loaded, but the remainder is four clauses of permission gating that restate the same idea three ways ('check business permissions', 'call check_business_tool_access', 'never proceed when access is blocked'). The information is useful but could be compressed without loss.

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 two-required-parameter tool with full schema coverage and no output schema, the description covers the operation and its access preconditions adequately. The only soft spot is that 'metadata' is never enumerated, so the agent cannot preview the scope of the extraction.

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%, with both url and communityId already documented including the 'never invent an ID' constraint. The description adds no further meaning about either parameter, so the baseline of 3 applies.

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 first sentence gives a specific verb and resource: 'Extract metadata for an external product URL.' That is concrete enough for an agent to recognize the operation. It does not distinguish itself from the sibling update_external_product, so it stops short of a 5.

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?

Strong on gating conditions: FREE businesses are excluded outright, check_business_tool_access must run before input collection, and blocked access must never be overridden. What is missing is any guidance on when to choose this over update_external_product or the other external-product siblings, leaving the extract-vs-update routing implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources