Skip to main content
Glama
dinwal
by dinwal

library_list

Retrieve all content libraries and their IDs to organize social media content for scheduling and management.

Instructions

List all content libraries with their IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and handler logic for the 'library_list' tool, which calls the internal '/api/library_list' endpoint.
    server.tool(
      "library_list",
      "List all content libraries with their IDs",
      {},
      async () => {
        try {
          return toolResult(await callAPI("/api/library_list"));
        } catch (e) {
          return toolResult({ error: String(e) }, true);
        }
      }
    );
Behavior2/5

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

No annotations provided, so description carries full burden. Beyond implying read-only via 'List', it omits pagination behavior, caching policies, rate limits, or return structure details needed for safe invocation.

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?

Single sentence with zero waste. Verb, resource, and key output field (IDs) are front-loaded and dense with information.

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?

Adequate for a zero-parameter tool, but lacks output specification (no output schema exists) or context on what constitutes a 'content library'. Should indicate what data structures are returned beyond just IDs.

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?

Input schema has zero parameters, triggering baseline score of 4 per rubric. Description appropriately makes no parameter claims that would require documentation.

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?

States specific verb 'List' and resource 'content libraries with their IDs'. Distinguishes from sibling 'social_account_list' via resource naming, though could explicitly clarify relationship to 'add_content_in_library'.

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?

Provides no guidance on when to use versus siblings, prerequisites (e.g., authentication requirements), or that results are needed for 'add_content_in_library'. Lacks 'when-not' or alternative suggestions.

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/dinwal/recurpost-mcp'

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