Skip to main content
Glama

generate_and_update_signed_url

Generate a signed URL for a private bucket file and update it along with expiration timestamp in a database table.

Instructions

Generate a signed URL for a private bucket file and update the URL in a DB media table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name (e.g. prd_medias, pry_medias)
pathYesFile path in the bucket (e.g. aqc/aqc-105/250gr.jpeg)
expires_inNoExpiry in seconds (default: 1 year = 31536000)
tableYesTable to update (e.g. prd_medias, pry_medias, brd_medias)
id_columnNoPrimary key column name (default: id)id
id_valueYesValue of the primary key to match
url_columnNoColumn for signed URL (default: signed_url)signed_url
expires_at_columnNoColumn for expiration timestamp (default: signed_url_expires_at)signed_url_expires_at
Behavior3/5

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

With no annotations, the description carries full burden. It mentions the two-step action but omits details like whether the row must exist, overwrite behavior, failure handling, or authentication needs. 8 parameters suggest more behavioral context would help.

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?

One sentence of 16 words, no wasted words, front-loaded with the core action. Ideal conciseness.

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?

Given the complexity (8 params, two-step action), the description is minimal. No return value info (no output schema), no prerequisites or failure behavior. Adequate for simple cases but incomplete for sophisticated use.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema parameter descriptions, but the overall action context provides minimal semantic value.

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?

The description clearly states the tool generates a signed URL and updates a DB media table. It uses specific verbs and resources, and distinguishes from siblings like get_signed_url (which only generates) and upload_file.

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?

The description implies usage context (when both URL generation and DB update are needed), but does not explicitly state when not to use it or provide alternatives. Sibling tools like get_signed_url are implied as alternatives for read-only scenarios.

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/natuleadan/mcp-backend'

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