Skip to main content
Glama

Cite from a web page

cite_from_url
Read-only

Fetch a web page and format it as a citation in APA 7, MLA 9, Chicago, Harvard, IEEE, or BibTeX, reading title, site name, and date from the page, or from values you supply.

Instructions

Fetch a web page and format it as a website citation in APA 7, MLA 9, Chicago author date, Harvard, IEEE or BibTeX. It reads the page title, the site name and the date from the page. Inputs: url (a full web address), style (apa7, mla9, chicago-ad, harvard, ieee, bibtex or all), and optional title, site_name and date to replace what the page gives. Pass all to get all three styles in one reply, each one with its style name on the line above it. Pass bibtex to get one .bib entry for a reference manager. Example prompt: "Cite this page in APA: https://example.edu/study."

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "cite_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA full web address, like https://example.edu/study.
dateNoUse this date instead of the one on the page, like 2026-10-14 or October 14, 2026.
styleNoCitation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee, bibtex and ris (a .ris record for Zotero, EndNote and Mendeley), or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one.apa7
titleNoUse this title instead of the one on the page.
site_nameNoUse this site name instead of the one on the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • changedInput schema / properties / style / description
      Previous value: -"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee and bibtex, or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."New value: +"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee, bibtex and ris (a .ris record for Zotero, EndNote and Mendeley), or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."
  2. Changed1 schema field changedv0.1.7
    • changedInput schema / properties / style / description
      Previous value: -"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard and ieee, or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."New value: +"Citation style. Aliases such as APA, MLA 9 and Chicago are accepted. Valid styles: apa7, mla9, chicago-ad (Chicago author date), harvard, ieee and bibtex, or all to get APA 7, MLA 9 and Chicago author date in one reply with a label above each one."
  3. Addedv0.1.6

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description still adds useful context: it reads title, site name and date from the page, allows overriding them, and explains that 'all' returns three labeled citations in one reply. It omits failure behavior (unreachable page, missing metadata), which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and strong, but the 'Inputs:' enumeration largely duplicates the input schema field-by-field, and the example prompt repeats the same information a third time. Roughly a third of the text does not earn its place.

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?

With no output schema, the description usefully sketches the return shape for the 'all' mode (labeled citations, one per style) and for bibtex. For a single-fetch formatting tool with fully documented parameters, only network-failure behavior is missing.

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 the baseline is 3. The description restates the parameters rather than extending them, and its style list ('apa7, mla9, chicago-ad, harvard, ieee, bibtex or all') actually drops 'ris', which the schema does include – a small inconsistency that adds no meaning beyond the schema.

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?

The description opens with a specific verb and resource: 'Fetch a web page and format it as a website citation' in seven named styles. The web-page framing implicitly separates it from cite_from_doi, cite_from_isbn and cite_from_arxiv, though no sibling is named explicitly, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied ('Cite this page in APA: https://...') and the description explains the bibtex path for reference managers, but it never states when to prefer cite_from_doi or find_doi over this tool, nor any exclusions such as paywalled or non-HTML pages. The agent must infer routing from the input type.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.