Skip to main content
Glama

Claim a listing

toolfound_claim_listing

Claim an existing Toolfound listing as the product's owner (free). Claiming requires ownership verification, a magic link is sent to the email you provide (use an address at the product's domain), and meta-tag / DNS TXT verification also works. Claimed listings unlock editing, badges, analytics, and the optional open-to-acquisition flag.

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": {
      "slug": "<slug>",
      "email": "<email>"
    },
    "name": "toolfound_claim_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug of the listing to claim.
emailYesYour email, ideally at the product's own domain, receives the claim magic link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Your email — ideally at the product's own domain — receives the claim magic link."New value: +"Your email, ideally at the product's own domain, receives the claim magic link."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive, non-idempotent, open-world call, and the description adds the key consequence the annotations cannot express: an outbound magic-link email is sent to the supplied address as part of the operation. It also lists what claiming unlocks (editing, badges, analytics, acquisition flag). It does not say what the immediate response or failure modes look like.

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?

Two sentences, front-loaded with the action and cost, then the verification mechanics and payoff. Slightly dense but every clause carries information; 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?

For a two-parameter mutation with no output schema, the definition covers the side effect (email sent), the verification paths, and the resulting capabilities — enough to call it correctly. The remaining gap is outcome shape, which is minor given there is no output schema to lean on.

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%, so both parameters are already documented, including the domain-preference hint on email. The description reinforces the 'use an address at the product's domain' reasoning by tying it to verification, but adds no new syntax or constraints beyond the schema.

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 opens with a specific verb and resource ('Claim an existing Toolfound listing') and scopes it to the product owner, which separates it from a submission/creation flow. It stops short of naming a sibling like toolfound_submit_product, so the boundary is inferable rather than stated.

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?

It gives useful preconditions (ownership verification, email at the product's domain, alternative DNS/meta-tag routes) and tells the caller which email to supply. However, it never states when to choose this over a sibling such as toolfound_submit_product or when to follow up with toolfound_check_verification, so routing is implied.

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