FindAgent

findagent_edit_metadata

Idempotent

Edit the DISPLAY metadata of YOUR OWN PUBLISHED agent — title, tagline, description, example output, category (+ subcategories), tags, and the Tech Domain / Language facets (software agents). Pass the agent slug + only the fields you want to change. This does NOT change what the agent can DO: its tools/actions/credentials/prompts are unchanged (those re-version through your agent's own flow + admin review — findagent_bump_version for an agent built here, findagent_repull for an agent built from a code or skills repo, findagent_reintrospect_mcp for an external MCP listing), so a metadata edit goes live immediately without re-review. Owner-only. Existing buyers are unaffected. Use findagent_list_categories for valid category slugs.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Your published agent slug (you must own it).
`tags`	No	Replace the free-form lowercase tags (≤10).
`title`	No	New agent name (3–80 chars). Alias accepted: `name`.
`tagline`	No	New one-line value prop (10–140 chars).
`languages`	No	Replace the Language/Framework facets (slugs from findagent_list_tech_facets). Software-development agents only.
`description`	No	New description (50–4000 chars).
`tech_domains`	No	Replace the Tech Domain facets (slugs from findagent_list_tech_facets). Software-development agents only; ignored for any other discipline.
`category_slug`	No	New PRIMARY category: a TOP-LEVEL slug from findagent_list_categories. Alias accepted: `category`. When changing categories you must keep ≥1 discipline and a subcategory under every selected top-level (put the rest in additional_category_slugs).
`thumbnail_url`	No	The listing logo: a URL of an image already uploaded to this platform (anything else is refused). Pass an empty string to remove it, so the card draws a generated mark.
`example_output`	No	A real example of what this agent produces, shown on the listing labeled as creator-provided (markdown supported, ≤4000 chars). Optional; pass an empty string to remove it. This is a display example, not a live run.
`additional_category_slugs`	No	Replace the non-primary category memberships (≤12 slugs).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No
`updated`	No
`next_tool`	No
`ignored_note`	No
`instructions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / languages

Added value: +{
+  "description": "Replace the Language/Framework facets (slugs from findagent_list_tech_facets). Software-development agents only.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / tech_domains

Added value: +{
+  "description": "Replace the Tech Domain facets (slugs from findagent_list_tech_facets). Software-development agents only; ignored for any other discipline.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / thumbnail_url

Added value: +{
+  "description": "The listing logo: a URL of an image already uploaded to this platform (anything else is refused). Pass an empty string to remove it, so the card draws a generated mark.",
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that edits publish immediately without admin review, that the caller must own the agent, that existing buyers are unaffected, and that thumbnail/example_output are display-only artifacts (not a live run). This is rich behavioral context an agent cannot infer from readOnlyHint/idempotentHint alone.

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?

Dense but front-loaded: the core purpose leads, followed by the scoping disclaimer and sibling routing. The long parenthetical enumerating re-versioning paths is justified because it prevents misrouting, though it is the one place the prose could be tightened.

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

Completeness5/5

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

For an 11-parameter mutation tool with full schema coverage and an output schema, the description supplies everything an agent needs: editable fields, ownership requirement, immediate-publish behavior, sibling routing for non-display changes, and slug lookup pointers. No material gaps.

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 the schema carries most parameter detail. The description still adds partial-update semantics ('pass only the fields you want to change') and cross-references the lookup tools for valid category/facet slugs, which the schema itself does not.

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?

States a specific verb (Edit) and resource (DISPLAY metadata of YOUR OWN PUBLISHED agent), then enumerates exactly which fields are editable. It also names what the tool does NOT touch (tools/actions/credentials/prompts), which sharply distinguishes it from siblings like findagent_bump_version and findagent_repull.

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?

Explicitly states when to use it (display-only edits, go live immediately without re-review) and when not to (behavioral changes must route through bump_version, repull, or reintrospect_mcp). Adds the owner-only constraint and routes the agent to findagent_list_categories for valid slugs.

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

All FindAgent tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?