Skip to main content
Glama

ai_modeling_gallery_unlike

Remove a like from a Studio gallery model by ID to update its engagement status.

Instructions

Remove your like from a Studio gallery model.

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>"
    },
    "name": "ai_modeling_gallery_unlike"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds that the like is user-scoped ('your like'), but says nothing about idempotency, auth requirements, or failure behavior for a mutation, which leaves the agent guessing at edge cases.

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?

A single front-loaded sentence with no filler; the action and target appear in the first few words. Nothing could be removed without losing meaning.

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 one-parameter toggle with no output schema, the definition covers what the tool does and its annotations cover mutation safety. It is still thin on the information an agent needs to invoke it confidently: where the model id comes from, whether repeated calls are safe, and what the response indicates.

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 description coverage is 0%, so the single 'id' parameter is documented only by its pattern and length constraints. The description partially compensates by indicating the id refers to a Studio gallery model rather than a like record, but it does not state the id format or source (e.g., from a browse/search result).

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?

States a specific verb and resource ('Remove your like from a Studio gallery model'), which unambiguously separates it from ai_modeling_gallery_like and the broader collect/uncollect pair. It stops short of naming the inverse sibling or clarifying the like/collect distinction, so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer it should be called to undo a like, but the description gives no explicit when/when-not guidance, no mention of what happens when the model was never liked, and no pointer to ai_modeling_gallery_uncollect for the separate collection concept.

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

Deploy Server

Other Tools