Skip to main content
Glama

venice_list_api_keys

Retrieve all API keys associated with your Venice AI account to manage access and permissions for AI model interactions.

Instructions

List all API keys on the account (requires admin API key)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: fetches API keys via veniceAPI, processes the response, handles errors, and returns a formatted text list of keys.
    async () => {
      const response = await veniceAPI("/api_keys");
      const data = await response.json() as APIKeysResponse;
      if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
      const keys = data.data || [];
      const list = keys.map((k) => {
        const created = k.createdAt || k.created_at || "?";
        const name = k.name || k.description || "Unnamed";
        return `- ${name} (${k.id}) - created: ${created.split("T")[0]}`;
      }).join("\n");
      return { content: [{ type: "text" as const, text: `API Keys (${keys.length}):\n${list}` }] };
    }
  • Registration of the 'venice_list_api_keys' tool on the McpServer instance within the registerAdminTools function.
    server.tool(
      "venice_list_api_keys",
      "List all API keys on the account (requires admin API key)",
      {},
      async () => {
        const response = await veniceAPI("/api_keys");
        const data = await response.json() as APIKeysResponse;
        if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
        const keys = data.data || [];
        const list = keys.map((k) => {
          const created = k.createdAt || k.created_at || "?";
          const name = k.name || k.description || "Unnamed";
          return `- ${name} (${k.id}) - created: ${created.split("T")[0]}`;
        }).join("\n");
        return { content: [{ type: "text" as const, text: `API Keys (${keys.length}):\n${list}` }] };
      }
    );
Behavior3/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. It discloses the authentication requirement ('requires admin API key'), which is valuable behavioral context. However, it doesn't mention other traits like whether this is a read-only operation (implied by 'List'), potential rate limits, pagination, or return format. The description adds some value but leaves gaps in behavioral disclosure.

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 action ('List all API keys') and includes essential context ('requires admin API key'). There is no wasted verbiage, and every word earns its place, making it highly concise and well-structured.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is reasonably complete for a simple listing operation. It covers the purpose and authentication need. However, without annotations or output schema, it doesn't describe the return format (e.g., list structure, key fields) or other behavioral aspects like pagination, which could be helpful for an agent.

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?

The tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate. It implicitly confirms no parameters are needed by not mentioning any, which aligns with the schema.

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 'List' and the resource 'all API keys on the account', making the purpose specific and understandable. It distinguishes itself from siblings like 'venice_retrieve_api_key' (singular retrieval) and 'venice_create_api_key'/'venice_delete_api_key' (mutation operations). However, it doesn't explicitly differentiate from 'venice_list_characters' or 'venice_list_models' in terms of resource type beyond naming.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context with the prerequisite 'requires admin API key', indicating when this tool can be used (with admin privileges). It doesn't explicitly state when NOT to use it or name alternatives, but the sibling tools suggest this is for listing all keys rather than creating, deleting, or retrieving a single key.

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

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/georgeglarson/venice-mcp'

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