Skip to main content
Glama
Cicatriiz

Civitai MCP Server

get_creators

Search and browse Civitai's model creators by username, with options to filter results by page number and limit output to streamline discovery of AI model creators.

Instructions

Browse and search for model creators on Civitai

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of creators to return (0-200, default 20)
pageNoPage number for pagination
queryNoSearch query to filter creators by username

Implementation Reference

  • The primary handler function for the 'get_creators' MCP tool. It invokes the CivitaiClient's getCreators method, formats the response data into a readable text summary, and returns it in the MCP content format.
    private async getCreators(args: any) {
      const response = await this.client.getCreators(args);
      
      return {
        content: [
          {
            type: 'text',
            text: `Found ${response.metadata.totalItems || response.items.length} creators:\\n\\n${response.items.map(creator => 
              `**${creator.username}**\\n` +
              `Models: ${creator.modelCount || 0}\\n` +
              (creator.link ? `Profile: ${creator.link}\\n` : '') +
              '\\n'
            ).join('---\\n')}\\nPage ${response.metadata.currentPage || 1} of ${response.metadata.totalPages || 1}`,
          },
        ],
      };
    }
  • src/index.ts:194-205 (registration)
    Registration of the 'get_creators' tool in the MCP server's tool list, including name, description, and input schema definition.
    {
      name: 'get_creators',
      description: 'Browse and search for model creators on Civitai',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Number of creators to return (0-200, default 20)', minimum: 0, maximum: 200 },
          page: { type: 'number', description: 'Page number for pagination', minimum: 1 },
          query: { type: 'string', description: 'Search query to filter creators by username' },
        },
      },
    },
  • Zod schema for validating the CreatorsResponse from the Civitai API, used in the client implementation.
    export const CreatorsResponseSchema = z.object({
      items: z.array(CreatorSchema),
      metadata: MetadataSchema,
    });
  • Core API client method that performs the HTTP request to Civitai's /creators endpoint, builds the URL with parameters, and validates the response using the schema.
    async getCreators(params: CreatorsParams = {}): Promise<CreatorsResponse> {
      const url = this.buildUrl('/creators', params);
      return this.makeRequest<CreatorsResponse>(url, CreatorsResponseSchema);
    }
  • TypeScript interface defining the input parameters for the getCreators method, matching the tool's inputSchema.
    export interface CreatorsParams {
      limit?: number;
      page?: number;
      query?: string;
    }
  • Zod schema for individual Creator objects returned in the response.
    export const CreatorSchema = z.object({
      username: z.string(),
      image: z.string().nullable().optional(),
      modelCount: z.number().optional(),
      link: z.string().optional(),
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'browse and search' but doesn't specify if this is a read-only operation, whether it requires authentication, rate limits, pagination behavior beyond the schema, or what the output format looks like. This leaves significant gaps in understanding the tool's behavior.

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 directly states the tool's purpose without any fluff or redundant information. It's appropriately sized and front-loaded, 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 complexity of a search/browse tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what information is returned about creators, how results are structured, or any behavioral traits like error handling. This leaves the agent with insufficient context for effective use.

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?

The input schema has 100% description coverage, clearly documenting all three parameters (limit, page, query) with details like ranges and purposes. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline for high schema coverage without compensating value.

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 ('browse and search') and resource ('model creators on Civitai'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'search_models_by_creator' or 'get_latest_models', which might also involve creators, so it doesn't fully distinguish from alternatives.

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. It doesn't mention scenarios like when you need creator information specifically, or when to prefer other tools like 'search_models_by_creator' for models by a creator. Without such context, the agent lacks clear usage direction.

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