Skip to main content
Glama

helius_get_assets_by_creator

Retrieve assets created by a specific Solana address using Helius blockchain data. Input the creator address to fetch associated tokens and NFTs.

Instructions

Get assets created by a specific address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
creatorYes
pageNo
limitNo

Implementation Reference

  • The main handler function that executes the tool logic for 'helius_get_assets_by_creator'. It remaps the input parameters (creator to creatorAddress) and calls the Helius RPC method `getAssetsByCreator`.
    export const getAssetsByCreatorHandler = async (input: { creator: string, page?: number, limit?: number }): Promise<ToolResultSchema> => {
      try {
        // Fix the parameter name mismatch
        const params = {
          creatorAddress: input.creator, // Change creator to creatorAddress
          page: input.page || 1,
          limit: input.limit || 10
        };
        const assets = await (helius as any as Helius).rpc.getAssetsByCreator(params);
        return createSuccessResponse(`Assets by creator: ${JSON.stringify(assets, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting assets by creator: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The input schema definition for the 'helius_get_assets_by_creator' tool, specifying parameters like creator (required), page, and limit.
    {
      name: 'helius_get_assets_by_creator',
      description: 'Get assets created by a specific address',
      inputSchema: {
        type: 'object',
        properties: {
          creator: { type: 'string' },
          page: { type: 'number' },
          limit: { type: 'number' }
        },
        required: ['creator']
      }
    },
  • src/tools.ts:578-578 (registration)
    The registration mapping that associates the tool name 'helius_get_assets_by_creator' with its handler function helius.getAssetsByCreatorHandler in the handlers dictionary.
    "helius_get_assets_by_creator": helius.getAssetsByCreatorHandler,
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It does not disclose behavioral traits like pagination behavior (implied by 'page' and 'limit' parameters), rate limits, authentication needs, error conditions, or what 'assets' entail (e.g., NFTs, tokens). This leaves significant gaps for a read 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 with no wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, return values, and context needed for effective use, especially compared to sibling tools. This is a read tool with multiple parameters, requiring more guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter details. It mentions 'specific address' which hints at the 'creator' parameter, but does not explain 'page' or 'limit' (e.g., pagination defaults, range limits) or provide any semantic context beyond the schema's basic types.

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 'Get assets created by a specific address' clearly states the verb ('Get') and resource ('assets'), specifying they are filtered by creator address. It distinguishes from siblings like 'helius_get_assets_by_owner' or 'helius_get_assets_by_authority' by focusing on creator, but does not explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives such as 'helius_get_assets_by_owner' or 'helius_search_assets'. The description implies usage for assets created by a specific address, but lacks explicit context, prerequisites, or exclusions.

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/dcSpark/mcp-server-helius'

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