Skip to main content
Glama
Cicatriiz

Civitai MCP Server

search_models_by_creator

Discover AI models created by a specific user on Civitai. Filter results by username, limit the number of models, and sort by highest rated, most downloaded, or newest for targeted searches.

Instructions

Search for models by a specific creator

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of models to return (default: 20)
sortNoSort order for results
usernameYesCreator username to search for

Implementation Reference

  • MCP tool handler that executes the search_models_by_creator tool: calls client method, formats results into markdown text response.
    private async searchModelsByCreator(args: any) {
      const response = await this.client.searchModelsByCreator(args.username, args);
      const formatted = this.formatModelsResponse(response);
      
      return {
        content: [
          {
            type: 'text',
            text: `# Models by ${args.username}\\n\\n${formatted.models.map((model: any) => 
              `**${model.name}** (${model.type})\\n` +
              `Downloads: ${model.stats.downloads.toLocaleString()} | Rating: ${model.stats.rating.toFixed(1)}\\n` +
              `Tags: ${model.tags.join(', ')}\\n` +
              `${model.description}\\n\\n`
            ).join('---\\n')}`,
          },
        ],
      };
    }
  • Tool schema definition including input schema with required 'username' and optional limit/sort parameters.
    {
      name: 'search_models_by_creator',
      description: 'Search for models by a specific creator',
      inputSchema: {
        type: 'object',
        properties: {
          username: { type: 'string', description: 'Creator username to search for' },
          limit: { type: 'number', description: 'Number of models to return (default: 20)', minimum: 1, maximum: 100 },
          sort: { 
            type: 'string', 
            enum: ['Highest Rated', 'Most Downloaded', 'Newest'],
            description: 'Sort order for results'
          },
        },
        required: ['username'],
      },
    },
  • src/index.ts:71-72 (registration)
    Tool dispatching/registration in the CallToolRequest handler switch statement.
    case 'search_models_by_creator':
      return await this.searchModelsByCreator(args);
  • Client helper method that calls Civitai API's getModels with 'username' filter parameter.
    async searchModelsByCreator(username: string, options: Partial<ModelsParams> = {}): Promise<ModelsResponse> {
      return this.getModels({ username, ...options });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Search') but doesn't describe what the search returns (e.g., list of models with metadata), whether it's paginated, rate-limited, or requires authentication. This leaves significant gaps in understanding the tool's behavior beyond the basic operation.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded with the main action and resource, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a search tool. It doesn't explain what the return values are (e.g., model objects, metadata), how results are structured, or any behavioral traits like pagination or error handling. This leaves the agent with insufficient context to use the tool effectively.

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 100%, so the schema already documents all parameters (username, limit, sort) with descriptions and constraints. The description adds no additional meaning beyond implying the username parameter is central, which is already clear from the schema. This meets the baseline for high schema coverage.

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 verb ('Search') and resource ('models') with a specific filter criterion ('by a specific creator'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_models' or 'get_creators', which would require more specific language about scope or output format.

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. With siblings like 'search_models', 'get_creators', and 'get_latest_models', there's no indication of when this specific creator-based search is preferred or what distinguishes it from other search or retrieval tools.

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

Related 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/Cicatriiz/civitai-mcp-server'

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