Skip to main content
Glama

unlink_external_product

Disassociate an external product from a subscription product to correct billing records.

Instructions

Unlink an external product from a product. DELETE /products/{productId}/external-products/{externalProductId}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdYesProduct ID (required)
externalProductIdYesExternal product ID (required)

Implementation Reference

  • Handler function for unlink_external_product. Parses args with Zod schema, validates productId and externalProductId, then calls the service layer to DELETE the external product link.
    async function handler(client: Client, args: Record<string, unknown> | undefined) {
      const parsed = schema.safeParse(args);
      if (!parsed.success) {
        return errorResult(parsed.error.errors.map((e) => e.message).join("; "));
      }
      const { productId, externalProductId } = parsed.data;
      return handleToolCall(() =>
        productService.unlinkExternalProduct(client, productId, externalProductId)
      );
    }
  • Zod validation schema requiring productId and externalProductId (non-empty strings).
    const schema = z.object({
      productId: z.string().min(1, "productId is required"),
      externalProductId: z.string().min(1, "externalProductId is required"),
    });
  • The tool is registered as part of the product tools array returned by registerProductTools().
      unlinkExternalProductTool,
    ];
  • Service helper that performs the DELETE /products/{productId}/external-products/{externalProductId} API call.
    export async function unlinkExternalProduct(
      client: Client,
      productId: string,
      externalProductId: string
    ): Promise<unknown> {
      return client.delete<unknown>(`/products/${productId}/external-products/${externalProductId}`);
    }
Behavior2/5

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

No annotations exist, and the description only mentions the endpoint (DELETE), implying destruction but not explicitly stating side effects, idempotency, or required permissions. Minimal behavioral disclosure.

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 very concise (one sentence plus endpoint), with no redundant information. However, it could include more context without being verbose.

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?

For a simple tool with two parameters and no output schema, the description is mostly adequate but lacks behavioral context (e.g., reversibility, concurrency behavior).

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?

The input schema already describes both parameters with 100% coverage. The description adds no additional semantic meaning beyond what the schema provides.

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 clearly states the action ('Unlink an external product from a product') and provides the HTTP endpoint, making the purpose unambiguous. It also distinguishes from the sibling 'link_external_product'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, such as when to unlink vs. simply delete or update. No prerequisites or context for usage provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhinosaas/rebillia-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server