Skip to main content
Glama

manus_file_detail

Retrieve a file's metadata, including upload status, size, and expiration, by providing its file ID.

Instructions

Get a file's metadata including upload status, size, and expiration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYes

Implementation Reference

  • The handler function for manus_file_detail. Calls the /v2/file.detail API endpoint with a FileDetailQuery and returns a FileDetailResponse.
    async def file_detail(q: FileDetailQuery, ctx: ToolCtx) -> FileDetailResponse:
        return await ctx.client.call(
            "GET",
            "/v2/file.detail",
            params=q.model_dump(exclude_none=True),
            response_model=FileDetailResponse,
            rate_limit_key="file.detail",
        )
  • Input schema (FileDetailQuery) for manus_file_detail - accepts a file_id string.
    class FileDetailQuery(ManusModel):
        file_id: str
  • Output schema (FileDetailResponse) for manus_file_detail - wraps a FileRecord.
    class FileDetailResponse(ResponseEnvelope):
        file: FileRecord
  • Registration of manus_file_detail via @manus_tool decorator with name, description, input_schema, and output_schema.
    @manus_tool(
        name="manus_file_detail",
        description="Get a file's metadata including upload status, size, and expiration.",
        input_schema=FileDetailQuery,
        output_schema=FileDetailResponse,
    )
Behavior2/5

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

No annotations provided. Description does not disclose safety traits (e.g., read-only, auth needs, rate limits). Merely states it gets metadata without noting side effects or constraints.

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, direct, and efficient. No redundant information.

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?

Given simplicity (1 param) and no output schema, description lists key metadata fields. Could add more behavioral context but largely sufficient for basic invocation.

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

Parameters1/5

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

Input schema has one required parameter (file_id) with 0% description coverage. Description does not mention this parameter or provide any additional semantic meaning.

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?

Clearly states it retrieves file metadata, listing specific fields (upload status, size, expiration). Distinguishes from sibling CRUD tools like manus_file_create, manus_file_delete, manus_file_upload.

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 explicit guidance on when to use this tool versus alternatives. Does not mention prerequisites or when not to use it.

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/aruxojuyu665/Manus-MCP'

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