civitai-mcp-ultimate

Overview Schema Source Related Servers Discussions Admin

get_creators

Read-onlyIdempotent

Browse and search model creators on Civitai to discover and filter content by author. Use queries and pagination to find specific creators.

Instructions

Browse and search model creators on Civitai.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_creators"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No
`limit`	No
`page`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Apr 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations cover key behavioral traits (read-only, non-destructive, idempotent, open-world), so the description adds limited value. It hints at browsing/searching functionality but doesn't disclose additional context like rate limits, authentication needs, or pagination behavior beyond what annotations provide, resulting in adequate but not rich transparency.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Browse and search model creators on Civitai') with zero wasted words. It's appropriately sized for the tool's complexity, making it easy to parse quickly.

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?

Given the tool's low complexity (3 optional parameters), rich annotations (covering safety and behavior), and the presence of an output schema (which handles return values), the description is reasonably complete. It states the purpose clearly but could improve by adding usage guidelines or parameter hints to fully compensate for the lack of schema descriptions.

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?

With 0% schema description coverage, the schema provides no parameter details, but the description doesn't compensate by explaining parameters like 'query', 'limit', or 'page'. It mentions 'browse and search', which loosely relates to 'query', but lacks specifics on usage or semantics, aligning with the baseline for high schema coverage scenarios despite the low coverage here.

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 clearly states the action ('Browse and search') and resource ('model creators on Civitai'), making the tool's purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'search_models' or 'get_tags' that might also involve browsing/searching different resources, missing explicit differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'search_models' or 'get_tags'. It mentions 'browse and search' but doesn't specify contexts, prerequisites, or exclusions, leaving the agent with minimal usage direction.

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