Skip to main content
Glama

get_app_actions

Retrieve action schemas for apps to understand required inputs, outputs, and credit costs when building workflow steps in the Agentled MCP Server.

Instructions

Get detailed action schemas for a specific app. Returns input parameters, output fields, and credit costs. Use this to understand exactly what inputs an action needs when building workflow steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe app ID (e.g., "agentled", "hunter", "web-scraping", "affinity-crm")

Implementation Reference

  • The tool 'get_app_actions' is registered here. It takes an appId as input and uses the AgentledClient to fetch actions.
        server.tool(
            'get_app_actions',
            `Get detailed action schemas for a specific app. Returns input parameters, output fields, and credit costs.
    Use this to understand exactly what inputs an action needs when building workflow steps.`,
            {
                appId: z.string().describe('The app ID (e.g., "agentled", "hunter", "web-scraping", "affinity-crm")'),
            },
            async ({ appId }, extra) => {
                const client = clientFactory(extra);
                const result = await client.getAppActions(appId);
                return {
                    content: [{
                        type: 'text' as const,
                        text: JSON.stringify(result, null, 2),
                    }],
                };
            }
        );
  • The implementation of the logic called by the 'get_app_actions' tool, which performs an HTTP request to the API.
    async getAppActions(appId: string) {
        return this.request(`/apps/${appId}/actions`);
    }

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

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