Skip to main content
Glama

akb_publish

Create a public share URL for documents, table queries, or files, with optional password, expiration, view limits, and section filtering. Accessible without authentication.

Instructions

Create a public share URL for a document, table query, or file. For a document or file, pass the resource uri. For a table query, pass the SQL plus vault (queries can span multiple vaults — list them in query_vault_names). Supports expiration, password protection, view count limits, snapshots, and section filtering. Returns a shareable URL accessible without authentication. Prefer public_url_full (absolute URL) when sharing the link with a user; fall back to public_url (relative path) only if public_url_full is null.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriNoResource URI to publish (document or file). Omit for table_query.
resource_typeNoType of resource to share. For document/file, also pass uri. For table_query, pass query_sql + vault.document
vaultNoVault name (required for resource_type=table_query)
query_sqlNoSELECT SQL with :param placeholders (for resource_type=table_query)
query_vault_namesNoVaults referenced by the query (defaults to [vault])
query_paramsNoParameter declarations: {name: {type, default, required}}
passwordNoPassword to protect the share
max_viewsNoAuto-expire after N views
expires_inNoExpiration: '1h', '7d', '30d', or 'never' (default)
titleNoOverride display title
modeNolive=query each request, snapshot=cache result in S3live
sectionNo(document) Filter to a specific heading section
allow_embedNoWhether the share can be embedded via iframe/oEmbed
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses supported features like expiration, password protection, view limits, snapshots, and section filtering. It also explains the output URL distinction. While lacking details on idempotency or side effects, it is fairly transparent for a creation tool.

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?

The description is concise (5 sentences) and front-loaded with the main purpose. Every sentence adds necessary information without redundancy. The structure is logical: purpose, parameter usage, features, output guidance.

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 13 parameters with 100% schema coverage and no output schema, the description covers all major aspects: resource type handling, optional features, and output fields. It could be more detailed about the exact response structure, but it is sufficiently complete for an AI agent to use correctly.

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?

With 100% schema coverage, baseline is 3. The description adds value by grouping parameters by resource type, explaining the relationship between uri, vault, query_sql, and resource_type, and giving guidance on public_url_full vs public_url. This goes beyond the schema definitions.

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 explicitly states the action ('Create a public share URL') and the resources (document, table query, file). It clearly differentiates from sibling tools like akb_unpublish or akb_publications by specifying the creation intent.

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 gives detailed usage guidance: for document/file pass uri, for table_query pass SQL and vault, and mentions preferring public_url_full. However, it does not explicitly state when not to use this tool or mention alternatives for similar actions.

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/dnotitia/akb'

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