Skip to main content
Glama

list_common_infos

List common information shared across your account, such as business hours or contact URLs. Filter results by folder or retrieve uncategorized items.

Instructions

共通情報(特定の友だちに紐づかず、アカウント全体で共有される固定値。例: 営業時間・定休日・問い合わせ先URLなど)の一覧を取得する。友だち情報(friend_info、友だちごとに値が異なる属性)とは別物。各要素は配信テンプレートやメッセージ本文からショートコード(shortcode_id)経由で差し込める。folder_id を指定するとそのフォルダ内のみに絞り込み、null を指定すると未分類フォルダのみになる。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo取得件数(最大1000、既定50)
cursorNo前回レスポンスの next_cursor を渡すとその続きから取得する
folder_idNo絞り込み対象のフォルダID(省略時は全フォルダ、null 指定で未分類のみ)
Behavior4/5

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

No annotations, but description explains it's a read operation, folder_id behavior (null vs omitted), and that elements are used via shortcodes. Lacks explicit safety note but is transparent enough.

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?

Concise, front-loaded with purpose, no redundant sentences. Efficiently covers key points.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, distinction, filtering, and usage. Could mention return format (likely array with pagination) but still very complete given no output schema.

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?

Schema has 100% coverage, but description adds value by explaining folder_id's special behavior (null=unclassified, omitted=all) and context about list parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists common infos (account-level fixed values), defines them, and distinguishes from friend infos. Sibling tools are about tags, friends, etc., so no ambiguity.

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?

Describes when to use (account-level static data), how it differs from friend infos, and folder filtering. No explicit 'when not to use' or alternatives, but context is clear.

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/mediiiiium/mcp-jp'

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